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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating the normalized fields returned, but says nothing about pagination (the 'page' param), result limits, or auth requirements. Adequate but not rich given annotations carry the safety burden.

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?

A single front-loaded sentence that leads with the action and scope. It is efficient overall, though the long parenthetical listing of return fields is somewhat dense and partially redundant with the output schema.

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 7-parameter search tool with 0% schema coverage, the description omits all filter semantics (price bounds, pet_type, star_sitter_only, paging) and gives no sibling routing. An output schema already exists, making the return-field enumeration the least necessary content while the missing parameter guidance is the most needed.

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 description coverage is 0% across 7 parameters, so the description must compensate. It names only location and service type, leaving page, pet_type, min_price, max_price, and star_sitter_only entirely undocumented in both schema and description.

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 (Search) and resource (Rover pet sitters/dog walkers) with an explicit scoping clause ('by location and service type'). An agent can distinguish this from rover_sitter_profile (detail) and rover_trainer_search without opening any schema.

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 implies the search context but never states when to use it versus rover_sitter_profile or rover_trainer_search, nor any prerequisites or exclusions. Usage is only inferable from the name and scope.

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