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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description does add real value beyond them: nullable fields signal that missing evidence is preserved rather than fabricated, and the warning that provider observations/estimates do not establish actual account performance is a genuinely useful caveat. It still says nothing about pagination despite a limit parameter, or about result volume/latency.

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 the purpose statement is front-loaded, with no filler sentences. However, the brevity comes at the cost of information density: two of the four sentences are caveats and one is an unexplained constraint ("No additional calls or fallback"), so the space is not spent where an agent needs it.

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 and 0% parameter documentation, the description must supply both the input contract and the shape of the result, and it supplies neither. The agent does not know what "target" is, what a "paid keyword rank" row contains, or how "limit" affects the response.

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 description coverage is 0%, so the description must carry the semantics of both parameters, and it carries neither. It never explains what "target" accepts (domain, URL, keyword, advertiser name) nor what "limit" bounds, even though the schema caps it at 100 with a default of 20.

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 phrase "Provider database paid keyword ranks with source measurement times" identifies the resource (paid keyword ranks) and its provenance, and the word "paid" does distinguish it from organic-keyword siblings. But it is a noun phrase with no verb, and it never clarifies what the single required input "target" refers to (a domain, a keyword, an advertiser?), so the agent cannot confidently map a request onto it.

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 choose this tool over the many adjacent SEO keyword tools (domain_ranked_keywords, keyword_metrics, site_keywords, ad_transparency_search). The closing sentence "No additional calls or fallback" is a behavioral constraint, not usage guidance, and it is too cryptic to route an agent.

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