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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds useful non-annotation context: it is part of the SEO Intelligence add-on and consumes add-on credits. It does not explain pagination, the effect of the refresh flag, or result caps, so it adds value but leaves meaningful behavioral gaps.

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?

Three compact sentences, front-loaded with the core purpose before cost and add-on caveats. Minor redundancy between 'Every organic keyword a domain ranks for' and 'the full SEO footprint', but nothing wasteful enough to hurt.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. However, with five undocumented parameters at 0% schema coverage and no guidance on alternative SEO tools, the definition is only adequately complete for a query tool of this scope.

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% across five parameters (limit, target, refresh, language, location). The description only clarifies that the target is a domain; it says nothing about limit defaults, refresh semantics, or language/location filtering, so it fails to compensate for the coverage gap.

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 names a specific resource and scope: every organic keyword a given domain (own or competitor) ranks for, with search volume and position. The 'organic' qualifier implicitly separates it from siblings like seo_paid_keywords, but no sibling is named explicitly, so it stops short of a 5.

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?

Usage is implied ('the full SEO footprint') but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance among the many SEO siblings (seo_keyword_research, seo_rank_history, keyword_report). The only concrete guidance is the credit-cost warning.

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