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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds genuinely new behavioral context that access preconditions (source ownership, version, expiry, membership) are validated at run time, and that the crawl sample is bounded and not exhaustive. It does not explain output shape or what happens on failed membership checks, but it goes well beyond the annotations.

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?

Four short sentences, front-loaded with what the tool produces, followed by validity preconditions and a scope caveat. No filler, though the vocabulary ('typed source evidence', 'missing-field diagnostics') is abstract without an output schema to anchor 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, four schema-unnamed parameters, and a required task_id whose origin is unexplained, the description leaves the core calling contract unclear. It covers data-scope and access caveats but not how to invoke the tool correctly.

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% for four parameters, so the description carries the full burden, yet it never mentions task_id, pageUrl, limit, or keywordLength. At best 'bounded crawl sample' faintly hints at a sampling limit, leaving every parameter's meaning and range undocumented in prose.

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?

States the resource (page keyword density) and the data basis (a bounded crawl sample), which conveys a topic more than a distinct action. It never says whether this analyzes a specific page URL, a task, or a domain, and it does not distinguish itself from near-neighbors such as nexscope_seo_page_keyword_intersection or nexscope_duplicate_page_content.

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 versus alternatives, no prerequisites for obtaining the task_id, and no guidance on choosing pageUrl or limit. The only context is a caveat about sample scope, which is not usage guidance.

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