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

The annotations only say readOnlyHint=false; the description explains why that matters, namely that reading a one-shot capsule consumes it and the tool returns 410 once the capsule has ended. This is exactly the destructive side-effect and terminal-error disclosure an agent needs before calling, and it goes well beyond the annotation.

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?

Three short sentences, front-loaded with the action and then the two behavioral facts that matter. Every sentence earns its place with no filler.

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 one-parameter retrieval tool with no output schema, the definition covers the action, the input form, the destructive consumption, and the 410 failure mode. It does not hint at the capsule's contents or shape, which is the only remaining gap.

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% and the single parameter's description already documents the hf_… token and accepted /h/ and /api/handoffs/ URL forms. The description's 'by its token or URL' merely restates that, adding no syntax or format detail beyond the schema, 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?

States a specific verb and resource: 'Read a handoff capsule by its token or URL.' The consumption semantics ('one-shot capsule is consumed by this read') further pin down what this tool uniquely does versus the sibling waystation_handoff_put. It stops short of naming an alternative, but the resource is specific enough that an agent can select it.

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 implied by the resource name – use it to retrieve a handoff capsule you already have a token/URL for. There is no explicit when-to-use versus waystation_read or waystation_handoff_put, and no stated prerequisites or exclusions. Adequate but leaves routing to inference.

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