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

The description provides detailed behavioral context beyond annotations: what happens to sold tickets, attached events, and new attachments. This fully explains the tool's effect, and there is no contradiction with the annotations (readOnlyHint=false, destructiveHint=false).

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 a single sentence that efficiently conveys key information without redundancy. However, it could be slightly restructured for even better scanability, but overall effective.

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?

The description covers behavioral impact well but lacks any mention of return value or success criteria, which is important since there is no output schema. It also omits prerequisites beyond deal_id. Adequate for a simple mutation but incomplete.

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 description mentions 'Requires deal_id' but does not explain what deal_id represents or how to obtain it. The 'reason' parameter is completely omitted. With 0% schema description coverage, the description fails to compensate and leaves parameter meanings unclear.

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 clearly states the verb 'end' and resource 'active deal'. It specifies the behavioral implications: sold tickets keep terms, attached events untouched, only new attachments stop, and that it's terminal for the thread. This distinguishes it from sibling tools like accept_deal and decline_deal.

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 description indicates when to use (active deals) and that it's terminal. It requires deal_id. However, it does not explicitly state when not to use or mention that the action is irreversible, though that can be inferred from 'terminal'.

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