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

Annotations already disclose readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds little beyond that: it does not say whether the previous recipient loses access, whether an email is dispatched, whether a comment is sent, or what state the agreement must be in. The 'reassign' wording is the only behavioral signal, and it is largely redundant with the tool name.

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 with a docs link, front-loaded with the action. Nothing is wasted, though the sentence carries almost no operational detail given the tool's complexity.

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?

This is a destructive, open-world mutation on a UUID-scoped resource with a nested body object and no output schema. The description omits the id requirement, the state preconditions, the fate of the prior recipient, and the side effects of add_recipient_as_cc, leaving the agent materially under-informed.

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 reported at 0% for the top-level envelope, and the description only hints at recipient_name and recipient_email. It says nothing about the required path id, the optional comments field, or add_recipient_as_cc, which alters behavior (previous recipient becomes a CC). With low schema coverage the description should compensate but does not.

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 and resource ('Reassign an agreement') plus the scope of the change ('to a different recipient with new name and email'), which distinguishes it from resend-agreement-email and send-agreement. It stops short of explicitly naming or contrasting those siblings, so it falls just below a 5.

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 when-to-use guidance, no prerequisites (e.g. agreement must be in a draft/sent state), and no mention of alternatives such as resend-agreement-email or send-agreement. The only pointer is an external docs URL, which the agent cannot rely on at selection time.

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