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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. On top of that the description discloses ordering ('nearest first') and the fact that each result reports whether its coverage radius reaches the address — real behavioral detail beyond the annotations, though limits/pagination behavior is still unstated.

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 concise, front-loaded sentences: the core capability and ordering come first, with the booking eligibility note last. The second sentence is somewhat tangential to finding stores but does not bloat the definition.

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?

With four parameters at 0% schema description coverage and no output schema, the description should carry more of the burden. It explains the conceptual return shape but leaves limit, radius_miles (units/filter semantics) and the robomart_version enum unexplained, so an agent cannot call it correctly from the description alone.

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 four parameters. The description never names address, limit, radius_miles or robomart_version, and only obliquely implies distance filtering via 'nearest first' and 'coverage radius reaches the address', leaving it unclear whether radius_miles is a search filter or just a reported attribute.

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 and resource ('find live open stores near a drop-off address') plus the ordering and per-result payload, so the purpose is unambiguous. It does not, however, explicitly differentiate itself from the sibling list_stores or check_coverage, which are the tools an agent would most plausibly confuse it with.

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?

There is no statement of when to pick this over list_stores or check_coverage, nor any exclusions or prerequisites. The closing sentence about booking from an open store gestures at downstream use but is not usage guidance for this tool itself.

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