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

Annotations already establish the safety profile (readOnly, non-destructive, idempotent, open-world). The description does add real behavioral context beyond them: guards for LLM refusals, 5xx crashes, and empty JSON, plus a 'cryptographic execution receipt'. But it never says what a guard trip actually produces (error vs. transformed payload) or how the receipt is surfaced, so the added context is suggestive rather than actionable.

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, front-loaded with the core function and followed by the protective behavior. Every clause is doing some work, though the coined guard names are longer than they need to be for the information conveyed.

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 full burden of explaining what comes back — yet it only alludes to a 'cryptographic execution receipt' without saying how or where it is returned. Failure semantics for the three named guards are also unspecified, which is a meaningful gap for a tool whose entire value proposition is guarding responses.

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 67%: url and body are documented in-schema, and method is self-documenting via enum+default. The description adds nothing about parameters, and its 'drop-in URL fetcher' framing arguably undersells the POST-with-body capability. With the schema carrying most of the burden, 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 states a concrete verb+resource: it fetches a URL and verifies the response through guards. It is clearly distinguishable from all siblings (reputation, oracle, escrow, audit, KYA, wallet risk), none of which fetch URLs. However, the purpose is wrapped in proprietary jargon ('Canonical LLM Refusal Guard') that obscures rather than sharpens what it actually does.

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?

There is no guidance on when to choose this over a plain HTTP fetch or over any sibling tool, and no stated preconditions or exclusions. 'Zero-config drop-in' implies a replacement for a bare fetcher, but the agent must infer that on its own.

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