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

The description adds important behavioral details beyond the annotations: atomicity (any failure causes whole call to fail and nothing billed) and the $0.10 per call cost. It also specifies the return structure (pass bool plus sub-results). These are not present in the annotations, which only cover read-only and idempotent hints. No contradiction.

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 four sentences, each conveying essential information: the scope, atomicity, pricing, and return format. It is front-loaded with the primary purpose and does not waste words.

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?

The description is complete given the tool's complexity: it explains the atomic behavior, cost, and return structure. An output schema exists, so return values are further specified. No critical information is missing for an agent to decide whether to use 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%, with the url parameter already described as 'Live, fetchable http(s) URL to audit.' The tool description does not provide additional parameter-specific information, so it meets the baseline for high coverage.

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 runs all four audits (wcag, seo, security, performance) against one URL, distinguishing it from the individual sibling tools. The verb 'runs' is specific and the scope 'against one URL' is explicit.

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 context is clear: this is the combined bundle for all four audits, implied by 'all four audits' and 'billed as a single call.' However, it does not explicitly state when to prefer individual tools over the bundle, so it lacks explicit when-not/alternatives guidance.

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