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

Descriptions adds specific content beyond annotation: it lists generators with 'medium and core strength'. Annotation already indicates readOnlyHint=true, which is consistent. No contradictions.

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?

Single sentence, no wasted words. Front-loaded with action and object.

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 parameterless listing tool with output schema present, description is complete. It explains what is listed and adds specificity about 'medium and core strength'.

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?

No parameters in schema, so description cannot add parameter-specific meaning. Baseline 4 for 0 parameters; description appropriately focuses on tool purpose.

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 'list' verb and specific resource 'supported generation targets (providers + models)' with attributes 'medium and core strength'. Distinguishes from sibling 'suggest_generator' which suggests rather than lists.

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?

Implies listing all available options, but no explicit guidance on when to use vs alternatives like 'suggest_generator'. Context suggests use for getting all supported generators.

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