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

With no annotations, the description carries the full burden. It does disclose real behavioral facts — a $0.50 charge with a first-free allowance and an HMAC receipt output — but says nothing about permissions, idempotency, whether the escrow is immutable or reversible, or what happens to the bundle after submission.

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?

A single sentence with no filler and the core action front-loaded, which is good. However, the arrow notation and parenthetical pricing make it cryptic rather than clear, so compactness comes at the cost of readability.

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 six-parameter tool with nested objects, no annotations, no output schema, and zero parameter documentation, the description is far too thin. Naming the receipt artifact helps, but an agent still cannot tell what to pass or what constraints apply.

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?

All six parameters (label, tools, bundle, directory, registry_server, domain_verification_token) have 0% schema description coverage, and the description explains none of them. The burden falls entirely on the description here and it provides no parameter meaning at all.

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 verb ('escrow') and resource ('submission bundle') plus the artifact produced ('HMAC retention receipt'), which is enough to distinguish it from retention_diff/retention_packet in spirit. It does not explicitly differentiate from those siblings, so it stops short of a 5.

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 escrow versus use retention_packet, retention_diff, or the watch_* tools, and no preconditions stated. The only context is pricing, which is not usage guidance.

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