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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond that: local businesses reply with prices in writing, the tool returns a link to send the job, and it explicitly does not book anyone or share contact details.

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 core operation and the returned link are front-loaded, and the sentences are efficient. "Local businesses reply with prices in writing" is slightly tangential but still useful context, and nothing is seriously bloated.

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 a rich output schema and full annotations, the description covers what the tool does, when to use it, and the key safety guarantee. It could still be more complete by noting the US-only scope or explicitly differentiating from siblings, but nothing essential is missing for correct invocation.

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%, and the schema already documents the ZIP pattern and the full trade enum with a Handyman fallback note. The description gives trade examples (plumbing, electrical, HVAC, cleaning, roofing) but does not add syntax or selection guidance beyond what the schema provides.

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 states a specific verb and resource: it counts local businesses near a US ZIP code for a given trade and returns a job-send link. That is far more specific than the title alone, but it never names or distinguishes itself from the sibling tools compare_a_quote and what_to_tell_a_pro.

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?

"Use it when someone needs a local pro for a home repair or service" gives a clear usage context. There are no explicit exclusions or named alternatives, so it stops short of the top score.

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