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

readOnlyHint=false is consistent with a write-like re-affirmation. The description adds genuine behavioral context beyond annotations: it does not prove identity or a later instance's consent, has no expiry, and specifies request_id retry semantics. This is real value beyond the single hint.

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?

Dense but front-loaded: the core action leads, followed by scope, retry semantics, and the alternative. Each sentence carries meaning, with only minor terseness in the safety caveat.

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 4-required-parameter mutation tool with no output schema and no annotations beyond readOnlyHint, the description covers retry/safety semantics well but is silent on the meaning of revision_id, signatory_key, and the const agree field, leaving a real 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 description coverage is 0%, so the description must carry parameter meaning, but it only explains request_id (fresh UUID, reuse for retries). The required revision_id, agree (const true), and signatory_key are left entirely to the schema with no added semantic guidance.

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 gives a specific verb (reaffirm) and resource (current active endorsed text/signature) and clearly frames it as an explicit re-endorsement after reading. It distinguishes itself from the sibling 'adopt_agreement', though it does not fully contrast with sign_accord or amend_report.

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 states the tool is optional with no expiry, and explicitly names the alternative and the condition that selects it: 'Use adopt_agreement to return after withdrawal or change text.' This gives when-to-use, when-not, and the routing alternative.

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