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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered; the description adds genuinely new facts — the page is fetched exactly once, no page content is returned, and no charge or resource creation occurs. That goes beyond the annotations, though rate limits or failure modes (what 'unfetchable' looks like) are not described.

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 core capability and its exclusions are front-loaded in the first sentence, with supporting detail after. The inline JSON example is slightly redundant with a 100%-covered one-parameter schema, which keeps it from a perfect score, but overall it is compact and well ordered.

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?

There is no output schema, so the description carries the return-value burden itself and does so by enumerating all five returned fields. Combined with the fetch-once and no-charge guarantees, an agent has everything needed to invoke this correctly for a single-URL, read-only tool.

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?

With one parameter at 100% schema coverage, the schema already documents the URL fully, including the bare-domain allowance and exclusions for search phrases and private networks. The description's example adds a small confirming illustration but no meaning not already in the structured field, so the baseline 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 states a specific verb and resource — fetch one public URL and return fetchability, size, final URL, title, and content hash — which is far more informative than the title's generic 'check a public page'. It also makes clear what it does not do (no page content, no payment, nothing created), which implicitly distinguishes it from monitor-creation siblings, but it never names a sibling tool outright.

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?

Usage is only implied: 'preflight' plus 'nothing is created or charged' hints this is a trial/lookup step before using fluxproof_create_monitor or fluxproof_check_now, but the description never says when to pick this over those tools. No explicit exclusions or prerequisites are given beyond the input constraint about public pages.

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