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

Annotations declare readOnlyHint=false and openWorldHint=true, i.e. a task-creating external call. The description does add genuine context beyond that: idempotency, input-order preservation, owner-only call history retention, a seven-day freshness rule, and the 'missing values are not zero' caveat. However much of it is opaque boilerplate ('Schema C1-1.0', 'Uses one fixed Nexscope task', 'apply only to dependent requests') that an agent cannot act on, and the async-ness is only implied by the callId retrieval URL.

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 free of filler paragraphs, but it is front-loaded with a restatement of the title rather than the actual purpose, and the remaining sentences are telegraphic fragments of mixed value. Nothing is padded, but the ordering wastes the highest-attention slot.

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?

For a task-creating (readOnlyHint=false), open-world tool with no output schema and four undocumented parameters, the description leaves too much unspecified: what the result payload contains, that retrieval requires polling/async handoff, and how it relates to sibling keyword tools. The retrieval URL and idempotency notes are useful fragments but not enough for an agent to invoke confidently.

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 burden, and it does not. 'Bounded keyword inputs' only weakly gestures at the minItems/maxItems=20 constraint already encoded in the schema, and nothing explains what `limit` bounds (keyword count? result count?), how `keywords` relate to 'category-based' behavior, or why market/language are fixed to US/en constants.

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 first sentence is essentially the title restated as a noun phrase ('Category-based Keyword Ideas') with no verb describing what the tool actually does or returns. Given ~10 near-identical siblings (nexscope_seo_keyword_expand, nexscope_seo_category_keywords, nexscope_seo_keyword_categories, nexscope_amazon_keyword_expansion), the lack of any differentiation is a serious gap. An agent cannot tell from this text whether it generates, expands, or classifies 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?

The only usage-shaped content is retrieval mechanics (GET endpoint or nexscope_seo_call_result) for fetching results after the call. There is no statement of when to choose this tool over the many keyword-expansion/category siblings, and no prerequisites, exclusions, or supported keyword categories. Selection between this and nexscope_seo_keyword_expand is left entirely to guesswork.

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