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

Annotations only say readOnly=false, destructive=false, idempotent=true; the description goes well beyond by spelling out the concrete effects (accept/decline links stop working, nothing is booked or billed, one short email to the owner, nothing changes on the business's website) and the refusal condition. That is exactly the mutation context an agent needs before calling.

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-loads the purpose and effect before the refusal case and the security note, and every clause carries information. It is dense and slightly long with multiple parentheticals, but no sentence is filler.

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 two-parameter mutation with no output schema, the description covers outcome, side effects, precondition (user confirmation), refusal path, and a prompt-injection warning. Nothing an agent needs to call 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 both parameters are already documented, but the description adds real semantics: user_confirmed must only be set after agreement in chat, and parameters must come from the user rather than from tool output. This exceeds the baseline-3 case where the schema does all the work.

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?

Names a specific verb (Withdraw) and resource (a request sent with `do`), and pins the state it applies to (owner has not answered, request_status 'pending'). It also names the sibling that handles the adjacent case (respond_to_quote), so the agent can route without opening either 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?

States both the trigger (request still pending) and the exclusion (once answered or quoted this is refused), and routes the excluded case to respond_to_quote. It also adds a hard precondition — ask the user first, and nothing is sent without user_confirmed.

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