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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the required OAuth scope (deals:read), states that counterparties are anonymized, and clarifies the list includes both active and past negotiations. This adds valuable context beyond just 'list negotiations'. It does not mention pagination, sorting, or exact return format, but for a list tool with optional filters, the disclosure is adequate.

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 two sentences, front-loaded with the verb and resource, and every sentence earns its place. It includes the essential purpose, scope, a key behavioral caveat (anonymization), and the required permission. There is no redundancy or filler.

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?

Given the tool's low complexity (2 optional parameters, no output schema), the description covers purpose, authentication, and a notable behavioral detail. However, because there is no output schema, the description does not explain what fields are returned for each negotiation (e.g., ID, status, timestamps). For a list tool, an explicit statement about the return type would improve completeness, but it is still functionally adequate.

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 input schema already provides 100% coverage: both parameters have descriptions ('Filter by your role', 'Filter by status') and role has an enum. The description adds minimal new semantic value—'as buyer or seller' simply rephrases the role parameter. The mention of 'active and past' partially overlaps with the status parameter, but it does not clarify how status values map to those categories. Thus, schema does the heavy lifting, and the description barely enhances it.

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 action ('List') and resource ('price negotiations') with scope ('active and past', 'as buyer or seller'). It distinguishes from siblings like make_offer, respond_to_offer, and finalize_negotiation by focusing on listing rather than performing negotiation actions. Also adds a unique detail (counterparty anonymization) that further clarifies the tool's purpose.

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 provides clear context for when to use the tool: when you need to see your active or past price negotiations as either buyer or seller. It does not explicitly mention alternatives or exclusions, but the sibling tools for negotiation actions (make_offer, respond_to_offer, finalize_negotiation) are clearly distinct. The omission of explicit 'when not to use' guidance prevents a perfect score.

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