feat(chat): rely fully on jsdoc to bring in description and schema

[seefeldb]

Summary by cubic

Tools now auto-generate their description and input schema from JSDoc/type info, removing manual JSONSchema and string descriptions. This simplifies tool authoring and enforces a clear “pattern or handler” contract.

• Refactors

  • Derive tool description and inputSchema from pattern.argumentSchema or handler.schema (via JSDoc); explicit fields remain optional overrides.
  • Normalize boolean schemas: true -> { type: "object" }, false -> {}.
  • BuiltInLLMTool is now an either/or union (pattern XOR handler); description is optional; BuiltInLLMParams.tools now uses this type.
  • Chatbot tools converted to typed request interfaces with JSDoc; removed manual JSONSchema and description strings.

• Migration

  • Remove explicit inputSchema/description from tools and document request types with JSDoc; keep description only if you need to override.
  • Provide either pattern or handler, not both.
  • If you relied on boolean schemas, note the normalization behavior above.

[Copilot]

Pull Request Overview

This PR refactors the LLM tool system to automatically extract tool descriptions and schemas from TypeScript/JSDoc comments instead of requiring manual specification. The change simplifies tool definitions by relying on TypeScript types and JSDoc annotations for metadata.

• Removes manual description and inputSchema properties from tool definitions
• Adds logic to extract schemas and descriptions from patterns/handlers automatically
• Updates type definitions to make description and inputSchema optional in BuiltInLLMTool

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.

File	Description
packages/runner/src/builtins/llm-dialog.ts	Implements schema extraction logic and fallback to JSDoc descriptions
packages/patterns/chatbot-tools.tsx	Removes manual tool schemas and adds JSDoc comments with type definitions
packages/api/index.ts	Updates BuiltInLLMTool type to make description and inputSchema optional

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[cubic-dev-ai]

3 issues found across 4 files

Prompt for AI agents (all 3 issues)

Understand the root cause of the following 3 issues and fix them.


<file name="packages/runner/src/builtins/llm-dialog.ts">

<violation number="1" location="packages/runner/src/builtins/llm-dialog.ts:440">
Converting boolean false schema to {} changes semantics from &quot;deny all&quot; to &quot;allow anything&quot;; use a non-boolean schema that matches nothing instead.</violation>

<violation number="2" location="packages/runner/src/builtins/llm-dialog.ts:443">
Potential runtime error: schema may be undefined when only inputSchema is provided; use optional chaining and prefer inputSchema.description first.</violation>
</file>

<file name="packages/api/index.ts">

<violation number="1" location="packages/api/index.ts:270">
Making description optional is a breaking type change for consumers expecting it to always exist; consider keeping description required or providing a transition path.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[bfollington]

LGTM but I am going to see if I can action some of the AI feedback before merging.