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

Goes well beyond annotations: it discloses that accepting immediately creates a confirmed order at the agreed price, explicitly that no payment method is charged, that the buyer pays later through the same flow as orders.place, and that an Authorization Bearer header is required. This is exactly the 'beyond structured fields' context the annotations (readOnly=false, destructive=true, openWorld=false) can't convey.

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 purpose, then the caller-role rules, then the side effects and auth requirement. Every sentence carries information, though the second and third sentences are dense and could be broken up for faster scanning.

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 it need not document return values, and it covers the remaining gaps: required auth header, role-based action constraints, preconditions on offer state, and the critical payment/order side effect. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds role-conditional semantics beyond the schema: which action values are valid for which caller and that counter_price is required for 'counter'. It does not restate offer_id's uuid format, which the schema already covers.

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?

Starts with a specific verb+resource ('Responds to a pending Make an Offer / bargaining offer') and immediately scopes which offer types it applies to. An agent can distinguish this from offers.make (creating) and orders.place without opening any schema.

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?

Explicitly branches on caller role: sellers must use accept/reject/counter on a pending offer; buyers must use accept_counter on a countered offer. It also states the required state each case, so the agent knows exactly when the call is legal and which enum value to pick.

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