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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds some value by framing the payload as static explanatory material (including 'limitations'), but it does not disclose important behavior such as whether the result is cached/static or how the optional category filter scopes the response.

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?

A single sentence with the resource front-loaded and the payload contents following. The list is dense but each item earns its place by telling the agent what it will receive; no filler or repetition.

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 needn't be re-explained, and the description still usefully previews the content scope. The only real gap is silence on the category filter and on the static nature of this reference material, which is minor given full schema coverage and annotations.

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 100% for the single optional 'category' parameter, so the schema already carries its meaning and example values. The description never mentions the category filter, adding no syntax or filtering semantics beyond what structured data provides, which lands on the baseline.

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 a specific verb and resource ('Get audit methodology') and then enumerates exactly what the resource contains: scoring, 159 checks across 16 categories, severity logic, data sources, and limitations. An agent can tell this apart from seo_audit or generate_fixes because it is clearly documentation about the audit rather than an audit action, though no sibling is named explicitly.

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 explicit statement of when to reach for this tool versus seo_audit, get_opportunities, or the other siblings, and no prerequisites or exclusions. The content enumeration only weakly implies usage (read this to understand scoring), which is less than clear context.

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