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

Goes well beyond the annotations by disclosing that returned scores are relative indices rather than percentages or absolute volumes, and that provider region IDs must be preserved on round-trip. It does not explain the response structure or any limits, but the index semantics are the critical behavioral fact and are stated clearly.

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 the core definition front-loaded and the caveat following immediately. No filler, though the final sentence is disconnected from any visible schema field.

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 carries the burden of explaining results, and it covers only the value semantics (relative index) without describing the shape of the regional breakdown or how many regions come back. Combined with an undocumented market parameter, it is adequate but incomplete.

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 50% (market is undocumented), so the description should compensate for those gaps, but it adds nothing about keywords, dates, or market. Worse, 'Preserve provider region IDs' references a region identifier that does not appear as a parameter at all, which can mislead an agent into looking for one.

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 verb and resource ('relative keyword interest across United States regions') and is clearly distinct from the demographics and history siblings by scope. It doesn't explicitly name those siblings, but the geographic framing makes the purpose 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?

Usage is only implied: an agent can infer this is the geo-breakdown variant versus nexscope_seo_keyword_interest_history (time series) or nexscope_seo_keyword_interest_demographics (audience). No explicit when-to-use or when-not-to-use guidance is given.

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