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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered structurally. The description adds one genuinely useful behavioral caveat — that a 'ready' state does not imply human review — but it leaves what 'ready' refers to undefined and says nothing about what is returned.

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 compact sentence that front-loads the action, with no wasted text. Its brevity is efficient, though it shades into under-specification rather than pure economy.

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?

With no output schema, no parameter documentation, and a one-line description, an agent lacks the essentials: what a proof represents, where to obtain a proof_id, and what the response contains. Only the readiness caveat is fully conveyed.

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%, so the single parameter 'proof_id' has no documented meaning, format, or provenance anywhere. The description does not compensate, giving no hint about where a valid proof_id comes from or what its constraints mean.

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?

The verb 'Read' and the resource 'proof' are identifiable, and 'owned' signals an access boundary. However, 'immutable exact proof' is undefined domain jargon, and with no sibling tool covering proofs there is no anchor to disambiguate what a proof actually is.

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 call this versus any other tool, nor prerequisites such as how ownership or readiness is established. The trailing clause is a caveat about interpretation, not a when/when-not rule.

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