Deposit SAP Escrow V2

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

Discloses that it's a write operation (non-readOnly), requires local signing, and has preconditions. Annotations already show it's not destructive nor idempotent. Does not detail return value but output schema exists.

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 concise sentences: function+constraint, alternative, and broader context. No unnecessary words, well-structured.

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 distinction, preconditions, and context. Output schema exists. Could elaborate on nonce or escrow V2 concept, but adequate given sibling tools and annotations.

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 parameters are well-documented in the schema. Description adds no additional detail beyond what's already in the parameter descriptions.

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?

Clearly states the tool's function: direct deposit into a V2 escrow for local-signers only. Distinguishes from the sibling sap_escrow_build_deposit_transaction for hosted users.

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 specifies when to use this tool (local-signer) and when to use the alternative (hosted users). Also provides broader context: payment/settlement flow, prerequisites like estimating state and requiring signer mode and MCP policy approval.

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