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

Beyond the readOnly/openWorld annotations, it discloses genuinely non-obvious behavior: each URL is fetched twice (vp-1) using the checker's own fetcher rather than the agent's, and the result is a signed pin_id with either a body_sha256 or a contains/json_fields fallback for pages that change on every load. It also explains the provenance guarantee the pin buys at receipt time. Nothing here contradicts readOnlyHint=true, since the fetch itself is non-destructive.

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 imperative and the trigger are front-loaded, and every clause (double fetch, fallback check types, downstream handoff) carries information. It is dense with internal shorthand (pb-1, vp-1, body_sha256, json_fields) that an agent must parse contextually, which is the only thing keeping it from a 5.

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 tool with no output schema, the description covers the full lifecycle: pre-work read, the artifacts produced, and how they are consumed at claim time. It omits failure modes (what happens if a fetch fails or the page is ambiguous) and any pin validity/expiry semantics, which matter for a workflow tool where the claim may be filed much later.

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 0%, so the description must carry the parameter meaning, and it does: the urls array is defined as the targets the work must not change, and the 3-item cap is tied to that purpose. It does not specify URL format expectations (absolute http/https, the 2000-char limit) or what happens if one URL is unreachable, leaving some semantics to inference.

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 and resource ("Pin... with up to 3 URLs") and states exactly what the tool produces: a signed pin_id plus a ready must_not_change check. It also distinguishes itself from the sibling that consumes the result (submit_claim), so an agent can tell it apart from verify_claim or submit_claim without opening any schema.

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?

Timing is explicit and unambiguous: "call this BEFORE you start" and "After the work, pass those checks unchanged in submit_claim's must_not_change." It names the downstream tool and the handoff contract, which is exactly the guidance an agent needs. It does not state when *not* to pin (e.g., for pages that cannot be pinned or work with no immutable dependency), so it falls short of a 5.

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