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

Annotations already declare readOnly/idempotent/non-destructive and openWorld=false, so safety is covered; the description adds real behavioral context beyond that (misspellings tolerated, ambiguity returns candidates, per-trade page URLs, and an explicit prohibition on booking for exclusive_link towns). It stops short of covering error behavior, unknown-town handling, or result volume/pagination.

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 operative instruction is correctly front-loaded, but the rest is one dense paragraph with stacked parentheticals ('booking_kind' values, examples, and the exclusive_link caveat nested mid-sentence) that is harder to scan than a short bulleted outcome list would be.

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 no output schema, the description still explains the return shape an agent must act on: booking_kind values, project naming, booking_url, per-trade page URLs, and the candidate list on ambiguity. That is enough to call the tool and interpret its result correctly.

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 100%, so the baseline is 3; the description adds one genuinely non-schema fact — that small misspellings in the town are tolerated — plus the slug-vs-name flexibility. The 'leave it out to see every trade' note for trade largely duplicates the schema's own wording, so the gain is modest rather than rich.

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: resolve a Massachusetts town and list per-trade whether estimate visits can be requested, with three explicit outcome states (marketplace / exclusive_link / none). The opening 'Use this first whenever someone asks for a contractor, a quote or an estimate visit' clearly separates it from find_contractors and the booking siblings without the agent 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?

Gives explicit precedence ('use this first'), then branches by outcome: book through tools for booking_kind 'marketplace', hand the homeowner booking_url and 'do not try to book through tools' for 'exclusive_link', and ask the homeowner which candidate they mean when the town is ambiguous. When-to-use, when-not-to-act, and the alternative are all spelled out.

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