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

Annotations already cover the safety profile (read-only, idempotent, non-destructive), and the description adds rich context beyond them: exact return contents (tagline, strengths, Dr. Waggs reality check, health watch, gear picks), the caveat that health items are tendencies not diagnoses, and widget-rendering behavior that instructs the agent to shorten its reply. This is information annotations cannot convey.

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?

Front-loads the triggering condition, routes to alternatives compactly, then describes the return. Every sentence earns its place with no restatement of the name, schema, or annotations.

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 single-param read-only tool with no output schema, the description fully specifies when to use it, what it returns, the widget-display behavior, and the health-disclaimer scope. Nothing an agent needs to call it correctly is missing.

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?

Only one parameter with 100% schema coverage including examples ('Corgi', 'german shepherd'), so the schema fully documents it. The description adds no format or syntax guidance beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb+resource (retrieve profile card for a breed) and explicitly distinguishes scope: 'ONE named breed' general overview. Names the exact siblings it is not (assess_breed_fit, compare_dog_breeds, estimate_dog_insurance_cost) with conditions that select each.

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?

Explicit when-to-use ('general overview of ONE named breed') and three explicit when-not-to-use alternatives with their triggering conditions (personal fit, comparing 2-3 breeds, vet costs). Nothing is left to inference.

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