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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description discloses non-obvious traits: results are bounded database facts with explicit missing evidence, missing values are not zero, output is not paginated, and owner-only results persist in call history with a seven-day freshness rule. These are real caveats an agent would otherwise not know, though the phrasing is generic boilerplate.

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?

The description is short and front-loaded, but several sentences read as generic platform boilerplate ('Prices and publication are unapproved') that appear unrelated to a keyword-listing tool, diluting the signal the agent needs.

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, no parameter descriptions, and no clarifying annotation set, the description should define the input target and the shape of results. Instead it leaves the single required parameter undefined and gives no indication of what keyword data 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%, so the description carries the full burden, yet it explains none of the four parameters. 'target' is required and critical but is never defined (domain? URL? category?), and 'limit' is not mentioned at all; market/language are consts so they are less harmed.

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's first sentence is a verbatim restatement of the title, 'Site Category Related Keywords', and never says what the tool actually returns or what 'target' refers to (a domain, a category ID, a name?). Against a sibling list that already contains nexscope_seo_category_keywords, nexscope_seo_keyword_categories, and nexscope_seo_domain_ranked_keywords, an agent has no way to tell this tool apart.

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?

No when-to-use, when-not-to-use, or alternative is named, even though near-identical SEO siblings (nexscope_seo_category_keywords, nexscope_seo_paid_keywords) exist. Only 'One fixed task; no pagination' and the freshness sentence hint at operational context, not selection guidance.

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