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

Annotations only declare readOnlyHint=true, and the description adds substantial context beyond that: no access logging, no notification to the author, exclusion of contact info, references, and attachments, no updates after subsequent edits, rejection when expired or the author is deactivated, and the instruction not to retry with case changes. This is exactly the behavioral depth the annotation alone lacks.

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?

The description is dense and front-loaded with the core action, and every clause carries information. Semicolon-separated clauses are efficient, though the single long sentence is a bit packed and would read better broken up.

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, the description still covers what the snapshot contains and excludes, the rejection conditions, and the alternatives. Nothing an agent needs in order to call this correctly is missing.

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%, so the token parameter is already fully documented. The description still adds real value by stating it also accepts a share link and by warning against case-altered retries, beyond the schema's 43-char base64url pattern.

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 description states a precise verb and resource: anonymously reading the frozen proposal snapshot identified by a 43-character token or share link. The 'frozen snapshot' framing and the read-only nature distinguish this clearly from the sibling tools that mutate cooperation shares.

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?

It explicitly names the alternatives and the conditions that select them: use redeem_cooperation_share to leave an archival redemption record, and use send_cooperation_interest (after authorization) to express interest. Both the when-to-use and the switch conditions are unambiguously set against the sibling tools.

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