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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it opens an interactive window the person drives, returns who the shop is and what it prices, and crucially sends nothing unless the person holds a time. That side-effect clarification is the kind of context annotations cannot express.

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?

The description is front-loaded with what happens (window opens, person drives it) and then the usage trigger and side-effect guarantee, with no filler sentences. It is dense but every clause carries information; only the run-on comma structure costs it a point.

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?

An output schema exists and annotations cover safety, so return values and idempotence need little prose, and the description closes the biggest ambiguity by stating nothing is sent unless the person acts. The remaining gap is the unaddressed relationship to the sibling get_quote, which an agent must disambiguate on its own.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains where business_id comes from (provider_business_id in the feed or a find_help answer). The description only says 'given its business_id', adding no syntax or sourcing detail beyond the schema, so the baseline 3 applies.

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 gives a concrete verb and resource: it opens HandledIQ's quote window for a single shop and lets the person browse prices and hold a time. This clearly separates it from hold_time and from the sibling get_quote's likely programmatic return, but it never names or contrasts those siblings directly, so the differentiation must be inferred.

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?

It states the triggering condition explicitly: use it when the person wants to see one shop's prices and pick a time on screen, given its business_id. There is no explicit when-not clause or named alternative (e.g., get_quote for a non-interactive quote), which is the main gap.

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