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

Adds substantial context beyond the annotations: the 20-item cap, the warning that place IDs from view=places are regions and not the review-link Place ID, and the server-side maps-key dependency that can disable town search. These are exactly the failure modes an agent would otherwise hit blind.

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?

Front-loaded with the resource and the default view before any caveats, and every clause carries information. The final maps-key sentence is terse to the point of being cryptic, but nothing is padded or repeated.

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 tells the agent what each view returns ('the current business type, country, and place list for one location') and covers the search dependency. Nothing needed to call this correctly is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: q is required for view=places (not stated in the schema), and it reinforces the account_id vs location_id preference and the Place ID confusion. Minor uplift only, since the schema descriptions carry most of the detail.

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?

Opens with a specific verb+resource ('Read Google Business service areas') and immediately defines scope ('the towns and postcodes a location covers, up to 20'). The two-view structure (areas vs places) makes the read-only counterpart to manage_google_business_service_area unmistakable.

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?

Explicitly states the default view, that q is required for view=places, and gives a fallback path ('add a place with its Place ID and name on the update instead') when no maps key is configured. It never names the sibling manage_google_business_service_area directly, so the write-vs-read routing is implied rather than stated.

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