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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond them: results are bounded/limited rather than paginated, missing values must not be treated as zero, and owner-only results persist in call history. However, the 'prices and publication are unapproved' and 'seven-day source-freshness' sentences are opaque boilerplate with no actionable meaning for this call.

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?

Short (five sentences) and front-loaded with the resource name, so it is not bloated. But most sentences are cryptic policy fragments ('Prices and publication are unapproved') that cost reading effort without adding usable information.

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?

A read-only lookup with four parameters, no output schema, and no schema descriptions needs the description to explain inputs and return shape; this one explains neither. An agent knows it is safe and bounded but not what to pass or what comes back.

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% and the description never mentions target, limit, market, or language. 'No pagination' and 'bounded' weakly imply the limit is a hard cap, but the required 'target' parameter — the whole point of the call — is completely undocumented, and market/language are fixed consts the agent gets no warning to omit.

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 opens by restating the title verbatim ('Domain Organic Ranked Keywords') and never explains in plain terms what is returned — presumably the organic keywords a target domain ranks for. Phrases like 'Bounded Nexscope database facts with explicit missing evidence' are internal jargon rather than a purpose statement, and no sibling (e.g. nexscope_seo_site_keywords, nexscope_seo_domain_rank_overview) is distinguished.

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?

'One fixed task; no pagination' hints at a single-mode call but gives no when-to-use guidance, no prerequisites, and no alternative tools for adjacent needs (rank history, backlinks, keyword intersection). The agent must infer selection purely from the tool name.

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