Audit a public webpage

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

Annotations already declare readOnlyHint and openWorldHint, so safety and network reach are covered. The description adds genuinely useful behavioral boundaries the annotations cannot convey — no JS rendering, no CWV measurement, no indexing verification — which directly shapes interpretation of results. It does not describe the shape or size of what comes back.

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?

Two sentences, zero filler, with the core action and scope front-loaded and the limitations following immediately. Every clause carries distinct information.

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 tool with full annotations and schema coverage, the description covers what it does and what it explicitly does not do. The remaining gap is that there is no output schema and the description says nothing about the response structure, leaving the agent to discover the result shape at call time.

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?

Only one parameter, and the schema documents it fully at 100% coverage ('Public HTTP or HTTPS page URL to inspect'), so baseline is 3. The description reinforces the public HTTP/HTTPS constraint but adds no format or validation detail beyond the schema's `format: uri`.

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?

States a specific verb pair and resource: 'Fetch and audit one public HTTP/HTTPS HTML page,' with the signal domain (technical SEO, page structure) named. The 'one ... page' scope implicitly separates it from edgeo_crawl_site, but no sibling is named, so routing still requires a small inference.

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 closing sentence gives explicit negative scope — no JavaScript rendering, no Core Web Vitals, no indexing verification — which tells an agent when this tool will under-deliver. It stops short of pointing to an alternative (e.g., use edgeo_crawl_site for multiple pages), so the when-to-use-instead half is missing.

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