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 'Safe, read-only CRO analysis. No file modifications' statement, reinforcing the annotation without contradicting it. It doesn't add details about rate limits or output format, but for a read-only audit tool the behavioral disclosure 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 core purpose appears in the first sentence, followed by a scoped list of audit elements, then usage and behavior sections. Every sentence earns its place with no 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?

For a single-parameter read-only audit tool with full schema coverage and no output schema, the description covers purpose, scope, usage boundaries, and safety. It doesn't describe the return format, but since there is no output schema and the tool is an audit, an agent can reasonably expect a report; this is a minor gap rather than a critical omission.

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 single 'target' parameter is fully documented in the schema. The description adds context about what the audit evaluates but doesn't add new parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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 ('Audits') and resource ('Conversion Rate Optimization (CRO) and user conversion signals'), then enumerates concrete elements (CTAs, contact channels, social proof, mobile buttons, risk reversal). This clearly distinguishes it from sibling SEO audit tools focused on on-page, technical, or content signals.

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?

Explicitly states when to use (landing pages, pricing pages, checkout/contact funnels) and when not to use (organic ranking signals), naming the alternative tools 'seo_audit_onpage' and 'seo_audit_technical'. This is exactly the kind of routing 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.