Check one public page's declared machine-readable basics

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

Beyond the annotations, the description discloses meaningful behavior: same-origin fetching of robots.txt, sitemap.xml and llms.txt, rejection of private networks and non-standard web ports, and the absence of API keys, HMAC receipts, ranking or answer-engine visibility measurement. This adds useful scope and limitation context, though it does not mention rate limits or missing-file behavior.

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 definition is two tightly packed sentences that front-load the trigger condition and primary action. Every clause adds either scope, output, or limitation information without repetition.

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?

An output schema exists, so return-value details need not be fully repeated, and the annotations already establish the safety profile. The description supplies the remaining critical context: what is fetched, which network targets are rejected, and which related capabilities are explicitly not provided.

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%, and the single url parameter is already documented with examples and the HTTPS default behavior for domains without a scheme. The description does not add parameter-specific meaning beyond the schema, so the baseline 3 is appropriate.

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) and precisely names the resource: one credential-free public HTTP(S) page plus its same-origin robots.txt, sitemap.xml and llms.txt. It also states the returned artifacts (signals, completeness, coverage, score), making the tool's purpose unmistakable.

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?

It clearly scopes usage with 'On explicit request' and 'credential-free public HTTP(S) page', and explicitly excludes private networks and non-standard web ports. There are no sibling tools to route between, so no alternative-tool guidance is needed, but it does not specify when not to use the tool beyond those network restrictions.

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