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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely useful behavioral context: results are a *sample*, listing records carry paid status and booking links, and addresses/coordinates must not be inferred from descriptions. It stops short of describing result shape or 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?

Three short sentences, front-loaded with the identification, followed by two handling rules. No filler, though the handling rules are stated as bare imperatives without surrounding context.

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 a 4-param read-only retrieval tool with no output schema, the description omits what a listing record contains beyond paid status/booking links, and does not mention result count or pagination. The safety and data-fidelity context is present, but an agent still cannot predict the returned structure.

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 only 25%, so the schema documents 'keyword' but leaves limit, market and language without descriptions. The description partially compensates by pinning the tool to US English, explaining the market and language constants, but says nothing about the limit parameter's meaning (1–20, default 10).

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 the specific resource: a Google Local Finder US-English sample of local listings, which is a concrete verb-less but identifiable retrieval operation. It is distinguishable from image/news/shopping siblings, though it never explicitly contrasts with the very close sibling nexscope_seo_google_maps_results.

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?

The only guidance given is about how to handle output ('Preserve paid status and booking links', 'Do not infer addresses'). There is no statement of when to use this versus nexscope_seo_google_maps_results or nexscope_seo_serp, and no prerequisites or exclusions.

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