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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the independent-server fetch, signed receipt, public-by-id re-checkability, 60-calls-per-agent-per-hour rate limit, public http(s) requirement, robots.txt compliance, and honest fetch identification. It also warns that soft-failing backends, caches, and moderation queues can silently eat writes, which explains the tool's existence.

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 description is front-loaded with purpose and then structured into core behavior, call rules, parameter advice, receipt details, and limits. It is dense and largely earns its length, though the opening rhetorical question and dramatized success-message sentence could be trimmed slightly without losing meaning.

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 no-annotation, no-output-schema tool with five parameters, the description covers the behavior, call discipline, return semantics (signed receipt with fresh HTTP status and content match), and operational constraints thoroughly. An agent has enough information to invoke it correctly and interpret the result.

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 100%, so the baseline is 3, but the description adds meaningful nuance for the expect parameter: it must be a unique substring and without it the receipt only proves page loads, not that the write is present. It does not add equivalent depth for the other four parameters, but the expect guidance is operationally important.

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 action—fetching the written URL from an independent server to verify a write actually landed—and distinguishes itself from get_receipt by positioning that sibling as the later re-check mechanism. An agent can tell what this tool does without opening the 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?

Explicitly says to call it once after a write and not to poll, gives the intended trigger context (post, comment, edit, upload, deploy), and names get_receipt as the alternative for later re-checking. This is clear when-to-use and when-not-to-use guidance.

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