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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this with 'Reads only.' It adds substantive behavioral context by specifying that missing fields are listed and one-sided gaps are flagged neutrally with implications for both parties. No contradiction exists.

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 compact, front-loads the key phrase 'before-you-send-it checklist,' and then elaborates with useful examples. The middle clause is slightly dense, but every part contributes meaning and there is no wasted content.

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 one-parameter, read-only tool with no output schema, the description conveys the main deliverable and gives concrete examples of what the checklist surfaces. It does not specify the exact response format or whether a summary verdict is returned, but the tool's low complexity makes this a minor 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?

The single required parameter is fully described in the schema (agreement id or client name, maxLength 200), and schema description coverage is 100%. The description does not add parameter-level detail, but the baseline of 3 applies because the schema already carries the burden.

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 defines a specific deliverable: a pre-send checklist for one agreement, listing every missing field and neutrally flagging one-sided gaps such as no termination clause or uncapped liability. This clearly distinguishes it from siblings like agreement_get (retrieval), agreement_render (document generation), and agreement_update_status (state change).

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?

The phrase 'before-you-send-it checklist' gives a clear trigger: use this when preparing to send an agreement. It does not explicitly name alternative tools or state when not to use it, but the read-only analytic purpose is unambiguous from context.

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