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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds real value by stating results are a US/en sample, organic-only, and that identifiers/CIDs/coordinates/rating scales should be preserved for fidelity. What it omits is result volume, ranking behavior, and pagination/limit effects, so it is solid but not rich.

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 with no filler; the US/en scoping is front-loaded and the data-fidelity caveat follows. Slightly jargon-heavy phrasing ('outside this projection') but nothing is redundant.

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 readOnly/openWorld annotations and no output schema, the description covers the key behavioral facts an agent needs: organic-only scope, locale restriction, and which field types to preserve on return. The only meaningful gap is that result count / limit behavior is unexplained, which is minor for a 4-parameter read tool.

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% (only keyword documented), so the description must compensate, and it partly does by stating 'US English', which reinforces the const market/language fields. However it says nothing about 'limit' (default 10, max 20) or what the keyword drives, leaving one parameter semantically thin.

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 identifies the resource (Google Maps organic results, US/en) but is phrased as a noun phrase without a clear verb and never contrasts itself with the very similar sibling nexscope_seo_google_local_finder_results or nexscope_seo_serp. An agent can guess it retrieves map listings, but the distinction from the local-finder sibling is left to inference.

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 many sibling SERP/local/maps tools, and no prerequisites or exclusions beyond 'paid map items are outside this projection'. That clause describes output scope, not when-to-use guidance.

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