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

Annotations only declare readOnlyHint=false and openWorldHint=true, which leaves the retrieval behavior ambiguous, and the description does not resolve that. It does add useful behavioral constraints beyond the annotations — preserve paid status and booking links, and don't derive addresses or coordinates — which signal data-fidelity rules for the returned listings. Result count, freshness, and whether the sample is a live SERP are undisclosed.

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?

Three short sentences, front-loaded with the source and scope, with each subsequent sentence contributing a distinct data-handling rule. No filler or restatement of the name.

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 and 25% parameter coverage, the description should explain what comes back; it hints at fields (paid status, booking links, addresses, coordinates) but never states result count, ordering, or how `limit` shapes the response. Adequate for orientation, insufficient for confident 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 description coverage is only 25%, with just `keyword` documented, so the description must carry more weight. 'US English' implicitly explains the fixed `market` and `language` constants, but `limit` (1-20, default 10) and the keyword-format rules are left entirely to the schema. It adds little beyond what the const defaults already communicate.

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 names a specific resource and source: a US English Google Local Finder sample of local listings. That is clearly distinct from the Maps, Shopping, or organic SERP siblings. It stops short of explicitly differentiating itself from the closest sibling (nexscope_seo_google_maps_results), so it is not a 5.

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?

There is no statement of when to call this versus the Maps or generic SERP tools, and no prerequisites or exclusions. The instruction 'Do not infer addresses or coordinates' governs post-processing of the data rather than tool selection, so it does not function as usage guidance.

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