seo_generate_marketing_strategy

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

With no annotations provided, the description carries the full burden, and it delivers via a dedicated 'BEHAVIORAL TRANSPARENCY' section: 'Safe, read-only strategic synthesis. Produces strategic Markdown plans without modifying any files.' This discloses read-only behavior, output format, and non-modification of files. No contradiction exists since annotations are absent.

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 core purpose is front-loaded in the first sentence, followed by compact, clearly delimited USAGE GUIDELINES and BEHAVIORAL TRANSPARENCY sections. Every sentence earns its place with no redundancy or filler.

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?

Given moderate complexity (2 params, no output schema, no annotations), the description covers purpose, usage boundaries against siblings, and behavioral transparency including output format. A minor gap is that it doesn't clarify its relationship to 'seo_generate_full_audit', another synthesizing sibling, though the strategic-marketing angle largely distinguishes it.

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 baseline is 3. The schema already fully defines both parameters ('target' as URL or file path, 'projectPath' as optional architecture context). The description adds no per-parameter meaning beyond the schema, so it stays at 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?

The description states a specific verb ('synthesizes audit findings') and a concrete deliverable ('high-impact digital marketing growth blueprint'), enumerating four explicit outputs (ToFu/MoFu/BoFu intent mapping, CRO levers, AEO tactics, 30-60-90 roadmap). This clearly distinguishes it from the 20 sibling audit, code-fix, and generation tools.

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 explicitly states when to use ('preparing a strategic marketing plan, client proposal, or business growth recommendations based on site audit data') and when not to use, naming two specific alternatives ('seo_generate_code_fix' for code fixes and 'seo_audit_technical' for quick diagnostics). This is model-friendly routing guidance.

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