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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description's 'Safe, read-only content analysis. No file modifications' largely restates the annotations with only marginal added context ('No file modifications'). It adds some value but not rich behavioral disclosure beyond what annotations provide.

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 main purpose is front-loaded in the first sentence, and the USAGE GUIDELINES and BEHAVIORAL TRANSPARENCY sections are short and purposeful. Slight redundancy exists where the behavioral section repeats annotation data, but overall structure is clean and efficient.

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 read-only analysis tool with a single, fully-documented parameter and safety annotations, the description covers what the tool audits, when to use it, and what to avoid. No output schema exists, but that is not a requirement for an audit tool. The only minor gap is that it doesn't describe the shape of the returned audit report, but this is acceptable given the audit context.

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% — the target parameter already carries a full description ('Target live URL or local file path to audit'). The tool description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb ('Evaluates') and a well-scoped resource (article/landing page content), listing concrete audit dimensions: content depth, search intent classification, word count thresholds, thin-content risks, reading ease, and E-E-A-T signals. This clearly distinguishes it from siblings like seo_audit_schema or seo_audit_technical.

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?

A dedicated USAGE GUIDELINES section states both when to use the tool (article/landing page editorial quality and intent alignment) and explicitly what not to use it for, naming two alternatives (seo_audit_schema and seo_generate_marketing_strategy). This is textbook when/when-not guidance with concrete alternatives.

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