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

Annotations declare the safety profile (not read-only, not destructive, not idempotent), and the description adds two things annotations cannot: the terminal state effect if accepted (case closes as settled without a verdict) and the authentication requirement ("Needs your API key"). It does not mention that a rejected offer leaves the case open pending a response, which is the main remaining behavioral gap.

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?

Three short sentences, front-loaded with the action and its consequence; nothing is padded. The trailing auth note is minor but not wasteful.

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 mutation tool with no output schema, the description covers the caller, the trigger condition, the accepted-outcome, and auth. It stops short of describing the non-accepted path or retry/idempotency behavior, which matters given idempotentHint=false but an idempotencyKey parameter.

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 caseId, terms, and idempotencyKey are all documented in the schema itself, and the description adds no parameter-level detail. Baseline 3 applies when the schema carries the full parameter burden.

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?

States a specific verb and resource (offers terms to the other side) and the resulting outcome (case closes as settled, no verdict). It distinguishes the action from the response/withdrawal siblings by describing who initiates, though it never names respond_to_settlement or withdraw_settlement_offer explicitly.

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?

"At any open stage" gives a usable timing precondition for when the tool applies. However, there is no guidance on the counterpart tools (responding to an offer, withdrawing one) or on what happens if the offer is declined, so the agent must infer the routing from sibling names alone.

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