sap_deposit_escrow_v2

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

No annotations are provided, so the description carries full burden. It merely says 'Deposit funds', implying mutation, but omits critical details: what happens to the escrow? Is there a return value? Are there side effects (e.g., changes to escrow state)? The agent cannot infer safety or reversibility.

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?

The description is a single, short sentence that front-loads the verb and resource. It is concise but arguably too terse; it could include a bit more context (e.g., 'Deposit lamports into a V2 escrow by nonce and agent wallet') without becoming verbose.

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?

Given the complexity of an escrow system and the absence of output schema or annotations, the description is incomplete. It does not explain what effect the deposit has on the escrow state, how to verify success, or whether there are any limitations (e.g., minimum/maximum amounts).

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?

With 100% schema description coverage, each parameter already has a clear description (nonce decimal string, amount in lamports, agent wallet base58). The tool description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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 clearly states the verb 'Deposit' and the resource 'V2 escrow', distinguishing it from v1 escrow operations. However, it does not explain what 'V2 escrow' refers to, but the context from sibling tools like 'sap_create_escrow_v2' and 'sap_withdraw_escrow_v2' helps disambiguate.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'sap_deposit_escrow' (v1) or other escrow operations. No mention of prerequisites (e.g., escrow must exist) or when not to use it.

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