Withdraw SAP Escrow V2

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

Annotations indicate destructive action; description adds specific behavioral constraints (local-signer-only, requires signer mode and policy approval) and context about write operations. No contradiction.

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?

Two sentences that are concise, front-loaded with the core action, and include necessary context without waste.

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?

Covers purpose, usage guidelines, prerequisites, and differentiates from sibling. Output schema exists so return values are covered elsewhere. Minor missing: no explanation of nonce default usage, but schema covers it.

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?

Input schema already describes all parameters with 100% coverage. Description does not add additional information about parameters beyond what is in the schema, so baseline 3.

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?

Description clearly states it is a direct withdrawal from a V2 escrow for local-signer-only, distinguishing it from the hosted user alternative sap_escrow_build_withdraw_transaction.

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 states when not to use (hosted users) and names the alternative tool. Also provides prerequisites and requirements (enabled signer mode, MCP policy approval).

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