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

Annotations already mark this as a non-read-only, non-destructive, non-idempotent action, and the description adds real behavioral context: acceptance only records a choice, no work starts and nothing is owed until payment, and quote actions require an unexpired quote. It omits what a repeat submission does (relevant given idempotentHint=false), keeping it from a 5.

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?

Four dense sentences with no filler; the privacy/identity constraint (private receipt_id) is front-loaded and each action rule earns its place. The middle sentences are packed tightly enough that a reader must parse carefully, so not a 5.

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 4-parameter, nested-schema mutation tool with no output schema, the description covers prerequisites, per-action requirements, the financial consequence of acceptance, and a privacy constraint. The main residual gap is the return value/next-step after responding, which is not addressed.

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 binding semantics the schema cannot express: which actions require a proposed scope, that correct_scope for an Answer also needs correction text, and that decline_quote may carry a budget counter-offer. The Brief/Map exception ('send a changed question as a new request') is genuinely beyond the schema.

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 the resource (SNTL's offer) and enumerates the four response actions with their distinct conditions, so an agent knows exactly what the tool does. It does not sharply position itself against its siblings beyond naming check_research_status, so it falls short of 5.

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 explicitly states the prerequisite ('Use check_research_status before responding') and gives per-action selection rules: confirm_scope/correct_scope answer a proposed scope, accept_quote/decline_quote answer an unexpired quote. It also routes a divergent case (Brief or Map corrections) to a new request rather than this tool.

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