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

Annotations declare the safety profile (mutation, non-destructive, non-idempotent, closed-world), so the description's burden is lower. It still adds real value by describing outcomes ('Returns authorized terms or no offer, contextual guidance and permitted next actions') and the round-based context model, going beyond the structured fields.

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?

Front-loaded with the core action in the first sentence, followed by two tight sentences covering optional inputs and returns. No filler, though the name/description mismatch ('submit_offer' vs 'request a quote') is a minor structural wrinkle.

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?

With an output schema present, return-value detail is already covered, and the description nonetheless summarizes the outcome shape and the negotiation-round model. Combined with 100% schema coverage and annotations, an agent has everything needed to invoke this correctly.

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 100%, so the schema already documents all four parameters in depth, including the nested ask/data shapes. The description touches on omitting `data` but adds no syntax or format beyond the schema, making the baseline 3 appropriate.

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 states a specific action ('Request a quote') and ties it to the negotiation flow with existing context. It is clear on its own but does not differentiate itself from siblings like haggl_accept_offer or haggl_get_offers, so an agent still needs the negotiation context to place it precisely.

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?

It gives implied usage guidance ('Buyer data and evidence can be omitted; relevant additional context can be supplied later within the remaining rounds'), which helps an agent decide how to call it early in a session. However, it never states when to use this versus alternatives such as accept_offer or get_bids, leaving the choice to inference.

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