on_page_audit

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

With no annotations, the description must carry the behavioral burden, and it does disclose the $2.50 price and the outputs. Yet it does not clarify what 'x402 on Base' means, whether the URL is fetched live, or any limitations or error behavior, leaving meaningful behavioral gaps.

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 purpose is front-loaded in one sentence and the returns are formatted as scannable bullets with no filler. A small deduction is taken for the cryptic 'x402 on Base' phrase, which is not explained and may confuse an agent.

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 one-parameter tool with no output schema, the description supplies the essential context: what the audit checks, what it returns, and what it costs. It does not detail response formatting or error behavior, but those are minor gaps given the return list.

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 coverage is 100%, and the single url parameter is already described in the input schema. The description adds no additional parameter-level semantics, so the baseline of 3 applies.

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 and resource: 'Run a comprehensive on-page SEO audit for a URL.' This unambiguously states the tool's function and, through the on-page framing, separates it from sibling tools such as keyword_research or serp_analysis.

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 gives clear context that this tool is for auditing a URL's on-page SEO elements, and the returns list signals the kinds of issues it addresses. However, it never explicitly names alternatives or states when not to use this tool, so it falls just short of fully explicit routing.

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