Scaffold Module from Existing Data

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that calls return a 'capability_unavailable' message and that it is local-runtime only. Annotations already declare readOnlyHint=true, etc., but description adds specific error behavior and environment constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, each serving a clear purpose: stating unavailability and redirecting. No wasted words; highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks details about the tool's actual function (scaffolding from existing data) and parameter roles. While the unavailability message is complete for this backend, a local-runtime agent would be left without guidance. Missing output schema info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no information about any of the four parameters (name, state, table, source). The agent cannot infer parameter meanings or usage from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not explain what the tool does when available; it focuses on unavailability. The title hints at 'scaffold module from existing data' but the description omits this. The agent is told it's unavailable, so purpose is clear in that limited sense.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Not available on this backend' and directs to use 'design_workflow' instead. Provides clear when-not-to-use and an alternative, which is excellent guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.