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

No annotations are supplied, so the description carries the full burden. It does disclose the authorization model for delete (owning agent key or one-time delete credential), which is real behavioral value, but it says nothing about irreversibility of deletion, whether reads are scoped/expiring, 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?

Three compact sentences, front-loaded with the read/delete split and then the credential rule; each sentence carries information. It stops short of waste, though the endpoint strings duplicate what the action names already convey.

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 tool with 11 parameters, a oneOf/anyOf conditional schema, a nested body object, no output schema, and no annotations, the description is far too thin. An agent cannot infer the purpose of most parameters or the shape of the response from this text alone.

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 only 9% across 11 parameters. The description mentions token (implicitly via the path) and delete_credential, but leaves id, handle, body, wanted_id, transfer_id, idempotency_key, and payment_signature entirely unexplained in both schema and prose, so it fails to compensate for the coverage gap.

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 pair and resource: 'Read or delete a saved check receipt,' and maps each action to its concrete endpoint (GET/DELETE /v1/check/reports/{token}). That is enough for an agent to know exactly what the tool does, though it never distinguishes itself from nearby siblings such as check_pack_get or check_received_work.

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?

The description tells the agent what credential each action needs ('Deletion requires the owning agent key or the one-time delete credential') and gives per-action endpoints, which implies when each mode applies. However, it offers no explicit when-to-use / when-not-to-use guidance relative to alternative tools, so usage is only inferred.

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