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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: 'No auth required, MIT licensed' and a concrete example of the output shape. No contradictions 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?

Two sentences, front-loaded with the primary action, then parameter option and licensing/read-only context. Every sentence earns its place and there is zero redundancy.

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, one-parameter, read-only list tool with a rich output schema and comprehensive annotations, the description covers everything an agent needs: what it lists, how sub-breeds are represented, how to request a flat list, and that no auth is required.

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% and the schema description already fully documents include_sub_breeds ('Include the nested sub-breeds array... Set false for a flat list of breed names only'). The tool description repeats this guidance and adds a clarifying example, which is helpful but not essential. Baseline 3 is appropriate when the schema already carries the semantic load.

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 opens with a specific verb and resource: 'List every dog breed in the Dog CEO database'. It also explains the nested sub-breeds behavior with a concrete example, making the tool's purpose unmistakable and clearly distinct from sibling tools like random_image or sub_breeds.

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 clear parameter-level guidance ('Set include_sub_breeds=false for a flat list of breed names only'), but it never explicitly tells the agent when to choose this tool over alternatives such as dogceo.breeds.sub_breeds. The context implies when this tool is appropriate, but no alternatives or exclusions are named.

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