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

With no annotations, the description must carry full behavioral burden. It does disclose two important traits: the operation is read-only ('cannot execute or pay') and it requires a credential. It omits permission/auth specifics, behavior on a missing or expired result, and any side effects or rate limits.

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, zero waste. The purpose leads and the critical constraint ('cannot execute or pay') is front-loaded and unambiguous.

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 recovery tool with no annotations, no output schema, and 0% schema coverage, the description covers the core intent and a key safety constraint but leaves parameter mapping, credential/authorization handling, and failure behavior undocumented. Adequate but with clear gaps.

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 description coverage is 0% for two required parameters (`name`, `arguments`), so the description must compensate. The phrase 'original input and credential' gestures at the inputs but never clearly maps to `name` vs `arguments`, leaving the agent to guess which field carries the tool identity versus the stored invocation payload.

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 (Read) applied to a specific resource (the stored outcome of an earlier native paid call), which is a clear, non-tautological purpose. It does not, however, name or distinguish itself from plausible siblings like `read` or `report_caller_result`, so it falls short of full sibling differentiation.

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?

Implied usage is clear: retrieve a prior paid result 'using its original input and credential.' The clause 'This call cannot execute or pay' usefully distinguishes it from the original paying operation, but there is no explicit when/when-not guidance or named alternative for cases where recovery is not appropriate.

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