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

Adds substantial context beyond annotations: ordering method (straight-line distance), handling of missing addresses or closed sales, and the Google Maps link output. Annotations declare read-only/non-destructive, and the description complements them with operational behavior. Could note whether the returned hours reflect that day specifically, but generally rich.

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 core action and constraints, then the fallback behavior. No filler.

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?

Covers inputs, processing logic, and output form (hours, map link). Missing specifics on the exact return structure and how start_latitude/longitude relate to start_city, but adequate for correct invocation given no output schema.

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 60%, so some parameters lack descriptions. The description adds contextual meaning for date (defaults to the day most sales are open is in the schema, not here) and starting point, but start_latitude/start_longitude are undocumented in both schema and description. Baseline is 3 given the moderate coverage and the description's general helpfulness without filling every gap.

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?

Precise verb+resource+scope: 'Put 2 to 10 estate sales in driving order for one day.' Clearly distinguishes from siblings like search_estate_sales (finding sales) and get_estate_sale (details for one), since this composes multiple sales into a route.

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?

States the input count constraint (2-10) and that ordering is by straight-line distance. Explains what happens to unsuitable sales. Doesn't name alternatives explicitly, but the purpose is unambiguous enough to imply when to use it.

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