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 covered. The description adds a clear statement that it makes no modifications to codebase or remote sites, which reinforces the read-only nature and adds context beyond the annotations. It doesn't disclose rate limits or data source specifics, but for a read-only analysis tool this is adequate.

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 compact and front-loaded: the first sentence states the core purpose, and the USAGE GUIDELINES and BEHAVIORAL TRANSPARENCY sections are each one or two sentences with no filler. Every sentence earns its place.

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 single-parameter, read-only analysis tool with no output schema, the description covers the purpose, usage boundaries, and safety profile. It doesn't describe the return format, but with no output schema and a simple input, an agent has enough to invoke it correctly. Minor gap: it doesn't mention whether the target must be a local path vs. live URL, but the schema already covers that.

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%, so the schema already fully documents the single 'target' parameter. The description adds context about what the tool does with that target but doesn't add parameter-level detail beyond the schema. Baseline 3 is appropriate when the schema carries the full parameter documentation burden.

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 uses a specific verb ('Analyzes') and names the resource ('a website') and the four concrete outputs: market vertical, competitor archetypes, backlink/directory targets, and keyword topic clusters. This clearly distinguishes it from sibling audit tools like seo_audit_onpage or seo_generate_code_fix, which focus on different concerns.

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 USAGE GUIDELINES section explicitly states when to use the tool (expand organic reach, plan off-page directory submissions, identify competitor benchmarks) and explicitly names two sibling tools to avoid: seo_generate_code_fix for on-page code repairs and seo_test_web_mcp for protocol validation. This is exactly the kind of when/when-not guidance an agent needs.

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