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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: each result carries trust tier, distance, phone, profile and Trust Card links, free repair guides are returned first for matching appliance queries, and commercial-only shops are filtered out by default.

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 purpose is front-loaded in the first clause, followed by the conditional rules. The long inline enumeration of 44 categories overlaps heavily with the schema enum, but it does add human-readable labels the enum lacks, so it mostly earns its space even though the prose is dense.

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?

For an 8-parameter read-only search with no output schema, the description covers the return payload (trust tier, distance, phone, links), the guide-first behavior, and the commercial filtering rule. Gaps are minor: limit behavior and lang's practical effect are left to the 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?

With 75% schema coverage the baseline is already ~3, and the description goes further by explaining interaction semantics the schema does not: that brand/appliance/problem narrow appliance results and drive guide matching while other trades ignore them, and that segment controls the commercial inclusion rule. It does not explain limit (capped at 10) or lang's effect beyond the schema's own note.

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 opening sentence states a specific verb and resource ('Find local service businesses near a US ZIP code') and enumerates the supported service taxonomy, so the tool's scope is unmistakable. It never names the sibling tools (get_pro_profile, get_town_summary, what_breaks) or contrast itself with them, so it falls short of the 5-level sibling differentiation.

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 gives real conditional rules: brand/appliance/problem only narrow appliance-service queries and are ignored by other trades, and commercial-only shops are excluded unless segment is 'commercial'. What is missing is any explicit 'use this instead of X' routing or when-not-to-use guidance relative to the sibling tools.

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