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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond them: it does not say whether the previous recipient loses access, whether a notification is sent, or whether existing signatures are invalidated — significant omissions for a destructive reassignment.

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?

Two short sentences with the core action front-loaded and no padding. The second sentence is only a docs pointer, which is acceptable but not additive.

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 nested-body, destructive mutation with no output schema and no documented parameter semantics, so the description carries most of the explanatory burden — and it does not. An agent could call it, but would lack the operational context needed to do so confidently.

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?

Reported schema description coverage is 0%, and the description only mentions name and email. It does not explain the required agreement UUID path parameter, the optional 'comments' field, or the meaningful 'add_recipient_as_cc' flag that changes who retains visibility.

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+resource ('Reassign an agreement') and the payload it carries ('new name and email'), which distinguishes it from resend-agreement-email and update-draft-agreement. It does not explicitly name those near-siblings, but the operation is unambiguous.

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 reassign versus resend-agreement-email, void-agreement, or update-draft-agreement, and no stated prerequisites (e.g. agreement must be in a particular status). The agent must infer usage entirely.

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