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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds useful effect context ("no longer valid or executable"), but says nothing about irreversibility, required permissions, valid source states, or whether existing signatures remain accessible.

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 short sentence that front-loads the verb and effect with zero filler. Nothing could be removed without losing meaning.

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, likely irreversible state transition with no output schema to explain the result and no annotations covering prerequisites. The description omits valid starting states, permission requirements, downstream effects on signatures/attachments, and error behavior, leaving the agent under-informed for a one-way operation.

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?

There is a single required path parameter (id), and the schema itself supplies the UUID format, pattern and a short description of the field. With schema description coverage reported at 0%, the description contributes nothing about which agreement identifier is expected or how to obtain it, so it neither compensates nor harms.

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 pairs a specific verb ("Void") with a specific resource ("an agreement") and clarifies the resulting state ("no longer valid or executable"). It is clearly distinguishable in meaning from create/send/update siblings, but it never explicitly names or contrasts a sibling such as archive-template or update-draft-agreement.

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. only draft or sent agreements can be voided), and no mention of alternatives such as update-draft-agreement or send-agreement for cases where voiding is not appropriate. The agent must infer usage entirely from the name.

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