generate

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

Discloses key behaviors: generates based on symbol references, writes no files, returns a dictionary. With no annotations, description carries full burden and does so adequately, though could mention error handling.

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?

Moderate length with a logical structure: purpose, process, return format, parameters. No extraneous text, but could be slightly more 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?

Covers purpose, process, parameters, and return values. Without output schema, it lists return keys (files, referenced_symbols, stub_total_bytes), providing sufficient context for a generate tool.

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 has 0% description coverage; the description provides clear explanations for all three parameters in an 'Args' section, fully compensating for missing schema descriptions.

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?

Clearly states it generates minimal stub code for a stubbable package, specifying verb and resource. However, does not explicitly differentiate from sibling tool 'generate_submodule', leaving some ambiguity about scope.

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?

No guidance on when to use this tool versus alternatives like 'analyze' or 'generate_submodule'. The description is purely functional, lacking context for selection.

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