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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say the decline is final, what happens to the offer or any held funds, or how a terms_sha256 mismatch is handled — all material for an irreversible mutation.

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?

One short, front-loaded sentence with no filler, so there is no wasted wording. However, the brevity comes at the cost of the preconditions and consequences an agent needs, so it reads as under-specified rather than efficient.

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?

This is a destructive, irreversible mutation with no output schema and only half its parameters documented in the schema. The description should explain the inspect-then-decline flow, the role of the terms hash, and what success or failure looks like; it covers none of that.

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 50%: id and token carry descriptions, while reason and terms_sha256 do not. The phrase 'inspected terms' weakly points at terms_sha256 but never explains that it binds the decline to the exact terms version shown by inspect_offer, nor what happens if it is stale; reason's purpose is left entirely unstated. Baseline 3 given partial coverage, but the gap is not compensated.

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 names a specific verb ('Decline') and resource ('an issued offer'), which cleanly separates it from siblings accept_offer, counter_offer, and answer_remedy. The trailing phrase 'on its inspected terms' is opaque, but the core action is unambiguous.

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?

There is no explicit when-to-use guidance, no mention that inspect_offer must run first, and no statement of consequences versus accept_offer or counter_offer. 'On its inspected terms' faintly implies a prior inspection step, but the agent must guess at the prerequisite ordering.

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