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

The description states 'Safe, read-only strategic synthesis' and 'without modifying any files,' which aligns with annotations (readOnlyHint true, destructiveHint false). It adds value beyond annotations by disclosing the output format as 'strategic Markdown plans,' which is not present in the structured data. No contradictions with 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?

The description is well-organized with clear sections (purpose, usage guidelines, behavioral transparency) and front-loads the main action in the opening sentence. It is concise yet thorough, with no filler; every sentence contributes essential information for correct tool selection and invocation.

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 strategic synthesis tool with multiple outputs, the description covers purpose, usage, and behavioral traits. It lists the components of the blueprint and provides routing guidance. While it doesn't detail the exact Markdown structure, the description is sufficient for an agent to decide when to use it and what to expect. The absence of an output schema is partially mitigated by mentioning Markdown output.

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% (both target and projectPath have descriptive text in the schema). The tool description does not add parameter-specific guidance, but the schema already documents both parameters adequately. Thus, the description adds no extra semantic value beyond the schema, earning the baseline score of 3.

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 clearly states the tool 'Synthesizes audit findings into a high-impact digital marketing growth blueprint' and enumerates specific components (search intent mapping across ToFu/MoFu/BoFu, CRO levers, AEO tactics, 30-60-90 roadmap). It also differentiates from siblings by naming alternatives like seo_generate_code_fix and seo_audit_technical, making its unique role unambiguous.

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 description includes an explicit 'USAGE GUIDELINES' section with clear when-to-use scenarios ('Use when preparing a strategic marketing plan, client proposal, or business growth recommendations based on site audit data') and when-not-to-use exclusions with named alternatives ('Do NOT use to apply code fixes... use seo_generate_code_fix instead' and 'Do NOT use for quick technical diagnostic checks; use seo_audit_technical instead'). This provides complete routing guidance.

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