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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: the tool is free, results surface as a picker card in claude.ai, and there are exactly four styles per category. No contradiction with annotations.

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?

Three tight sentences, front-loaded with purpose, then cost, then usage workflow. The single-word sentence 'Free.' earns its place as a key behavioral fact, and nothing is redundant or padded.

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 simple read-only list tool with one optional parameter and rich annotations, the description covers purpose, categories, count, cost, and the consumption flow. With no output schema, it could have specified the exact return object shape in more detail, but it does state the critical fact that the result contains an id to pass to generate_image, which is what an agent needs.

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 coverage is 100%, setting the baseline at 3. The description adds real value by mapping the opaque enum values (cover-art) to human concepts ('album and podcast cover art') and clarifying the relationship between the category field and the enumerated looks. This helps an agent choose the correct enum value without opening the schema.

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 states a specific action (listing named styles) tied to a specific resource (generate_image) and enumerates the exact categories with a per-category count ('four styles each'). It is clearly distinguishable from siblings like list_models and list_generations by explicitly framing the output as the style picker for generate_image.

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?

The description gives an explicit trigger condition ('Call it when the person wants one of those') and a full follow-up workflow: show the picker, then pass the chosen id as style to generate_image. It lacks an explicit 'when not to use' or direct alternative naming for cases like video or editing, so it falls just short of a 5.

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