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

The annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that preparation is grounded in supplied commercial evidence, but it does not explain external inference processing, consent requirements, or what 'destructive' means in this context.

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 front-loaded sentence that names the core deliverables without filler. Every phrase contributes to the purpose statement.

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 complex tool with nested inputs, external-processing consent, payment handling, and no output schema, the description covers the main artifact set but omits source selection, consent, idempotency, and sibling alternatives. It is adequate but not complete enough for an agent to call the tool optimally without reading the full schema.

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 67%, with most nested input parameters documented in the schema itself. The description's phrase 'supplied commercial evidence' loosely relates to the inputs, but it does not clarify sourceFields, sourceRunIds, consentExternalProcessing, or idempotencyKey.

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 uses a specific verb, 'Prepare,' and names concrete negotiation artifacts: BATNA, reservation points, give/get trades, and buyer rehearsal. It is clear what the tool produces, but it does not distinguish itself from sibling tools such as xnegotiate-coach or the negotiation workflow tools.

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?

Usage is implied by 'grounded in supplied commercial evidence,' suggesting the tool is for negotiation preparation when commercial evidence is available. However, there is no explicit when-to-use guidance, no when-not guidance, and no comparison against alternatives in the large sibling toolset.

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