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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context including performance budget (8s per URL), cache TTL (1h), and the nature of the output (0-100 scores plus P0/P1/P2 recommendations). This goes 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 description is a single dense paragraph that front-loads the primary purpose and uses parenthetical lists to organize the many analysis areas. While not ultra-concise, every sentence carries meaningful information (scope, dimensions, options, ICP, performance constraints). It is well-structured for the complexity it conveys.

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 the complexity of the tool (four audit dimensions, optional competitor comparison, async mode, output schema), the description is remarkably complete. It explains the return format (scores and prioritized recommendations), performance limits, cache behavior, and target audience. It leaves little ambiguity about what the tool accomplishes.

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 all four parameters (url, mode, async, compare_competitors) are documented in the schema. The description adds only marginal value by mentioning competitor comparison and listing analysis dimensions that loosely map to mode values, but it does not introduce new parameter-level detail beyond the schema.

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 performs a 'Full SEO + CRO audit of any public URL' and enumerates the exact analysis areas (technical SEO, content SEO, performance signals, CRO). This specific verb+resource combination distinguishes it from sibling audit tools like privacy_compliance_audit or supplier_esg_audit.

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 provides clear context for when to use this tool by specifying the ICP (marketing managers, SEO/CRO consultants, e-commerce ops, agency teams) and the scope of analysis. It does not explicitly state when not to use it or name alternative tools, but the narrow focus on SEO+CRO makes this less critical.

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