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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description has to do the heavy lifting and it partially does: it discloses that the data is provider-sourced with measurement times, that nullable fields represent missing evidence, and that observations are estimates rather than actual account performance. That interpretation guidance is genuinely useful, but nothing is said about latency, result shape, or why a query-like tool is marked non-read-only.

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?

It is short and front-loads the resource, but four fragmentary sentences carry a lot of unexplained jargon ('source measurement times', 'preserve missing evidence', 'No additional calls or fallback') and never delivers a subject-verb statement of what is returned.

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, a required parameter with zero documentation, and no enumeration of what a paid keyword rank record contains, the description leaves an agent unable to call the tool correctly or interpret its output. It covers the caveats well but omits the essentials.

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 0% — neither 'target' (required) nor 'limit' has any description anywhere. The description does not compensate at all: it never mentions what target accepts (domain? keyword? advertiser ID?) or what limit bounds, leaving the required parameter undefined.

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 resource ('provider database paid keyword ranks') but supplies no verb and no scope: it never says whether it retrieves, lists, or ranks, nor whether 'target' is a domain, keyword, or advertiser. It is not a tautology of the title, but an agent cannot tell from this text what operation it performs or how it differs from the many sibling keyword tools (nexscope_seo_keyword_metrics, nexscope_seo_domain_ranked_keywords, nexscope_seo_site_keywords).

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 use this tool, when not to, or which sibling to pick instead. 'No additional calls or fallback' is an operational constraint, not routing guidance, and it is too cryptic to tell an agent what it should do when results are incomplete.

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