list_generators

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

With no annotations, the description carries the full burden. It clearly states the tool reads and lists generators with maturity and protocol capabilities, and the 'START HERE' cue implies it is a safe, read-only first step. However, it doesn't mention potential edge cases like pagination or rate limits, but for a simple list tool this is sufficient.

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, front-loaded with 'START HERE', and every clause earns its place. It defines the domain, states the output content, and provides next-step guidance—all without waste.

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?

For a 0-parameter tool with no output schema, the description fully covers what the tool does, what information it returns, and how to proceed. No gaps remain for the agent to make an informed selection.

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?

The tool has 0 parameters, so the baseline is 4. The description adds meaning by explaining that the output includes maturity and protocol capabilities, which helps the agent understand what to expect from the list.

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 uses a specific verb 'Lists' and explicitly defines the resource as 'every Packkit generator (a language target)'. It also distinguishes this tool from siblings by stating 'START HERE' and guiding to list_presets and get_generator_schema for subsequent steps.

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 tells the agent to start with this tool, then use list_presets and get_generator_schema before generating. This clearly states when to use this tool and the alternative/next actions.

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