seo_audit_conversion

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It explicitly says 'Safe, read-only CRO analysis. No file modifications,' which fully communicates the tool's safety profile. This is a sufficient and unambiguous disclosure for a read-only audit operation.

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 into purpose, usage guidelines, and behavioral transparency sections. The main sentence front-loads the verb and object, followed by a compact list of audited signals. Every line earns its place and there is no redundant fluff.

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 tool, the description is nearly complete: it covers what the tool audits, when to use it, alternatives, and safety. The only missing piece is the output format, but given the sibling 'seo_audit_*' family, an agent can reasonably infer the result is an audit report. This is a minor gap.

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?

The input schema already fully describes the only parameter 'target' as a live URL with an example. The tool description does not add additional parameter-level detail, though its usage guidelines hint at appropriate target URLs (landing pages, pricing pages, funnels). This is a standard baseline case where the schema does the heavy lifting.

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 opens with a specific verb ('Audits') and a specific resource ('Conversion Rate Optimization (CRO) and user conversion signals'), then enumerates concrete signals it checks (CTAs, contact channels, social proof, floating buttons, risk reversal). It also explicitly distinguishes itself from organic-ranking audit tools by naming seo_audit_onpage and seo_audit_technical as alternatives.

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 clearly states when to use the tool (landing pages, pricing pages, checkout/contact funnels) and when not to use it (organic ranking signals), naming the exact alternative tools. This gives the agent explicit routing rules with no left to inference.

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