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

The description discloses that the tool fetches the URL and returns a list of concrete issues, which complements the readOnlyHint and openWorldHint annotations. It clearly identifies it as a non-mutating, live-fetch operation without contradicting the annotations.

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 with the core action and resource, followed by a concise checklist of audited signals and a clear return type. Every sentence earns its place without redundancy or 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 one-parameter read-only tool, the description provides sufficient context: what it fetches, what signals it checks, what it returns, and its scope limitation. Even without an output schema, an agent can invoke it correctly and understand the result shape.

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 schema already documents the url parameter with a full URL example. The description adds value by clarifying the URL must be a single page rather than a domain or site root, reinforcing the parameter semantics 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 uses a specific verb ('Fetch a page and audit') and names concrete on-page SEO signals, making the tool's function unmistakable. The final sentence explicitly distinguishes it from a site crawl, which separates it from sibling tools like ai_crawler_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 clearly states that this tool handles a single page, not a site crawl, giving a useful exclusion for selection. It could be stronger by naming an alternative tool for site-wide audits, but the context is clear enough for an agent to decide when to use it.

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