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

The description adds real scoping beyond the sparse annotations: results are US-English only, organic only, and carry identifiers, string CIDs, coordinates, and rating scales. However, nothing is said about result volume, pagination, rate limits, or why readOnlyHint is false for what is plainly a retrieval call, leaving the behavioral profile incomplete.

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 core fact, with no filler. The second sentence reads more like a data-handling instruction to the agent than a tool description, but it is terse enough not to be a liability.

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 does give a partial picture of the returned fields (identifiers, CIDs, coordinates, ratings), which is helpful. It still omits how many records come back, whether the response is truncated by `limit`, and error/empty-result behavior, all of which an agent needs for a search tool with undocumented parameters.

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% — just the keyword field. The description conveys the fixed US/en market and language, which is already fully expressed by the const values in the schema, and says nothing about 'limit' (min 1, max 20, default 10) or how many results 'sample' implies. With low coverage the description should compensate for the undocumented limit parameter, and it does not.

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 US-English non-advertising results) but never states the action — that a keyword query is issued and local business listings are returned. It also does not differentiate from close siblings such as nexscope_seo_google_local_finder_results or nexscope_seo_serp, so an agent must infer the distinction from the tool name alone.

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 when-to-use guidance, no mention of what to use instead for local-pack lookups, paid map placements, or general SERPs, and no prerequisites. The exclusions present ('non-advertising', 'paid map items are outside this projection') describe output scope, not tool selection.

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