Fetch SAP Escrow V2

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. Description reinforces this by stating 'Read-only SAP SDK wrapper' but adds little extra beyond that. No contradictions.

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 sentences: core purpose, context, usage guidance. No redundant information. Front-loaded with the most critical information.

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?

With a complete output schema and clear annotations, the description sufficiently covers the tool's behavior and usage. It explains the fetch modes and the read-only nature.

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 covers all 4 parameters with individual descriptions. The description adds value by explaining the two valid parameter combinations (escrowPda alone or agentPda+depositor+nonce), which is not apparent from the schema alone.

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 the tool fetches a V2 escrow, specifying two lookup modes (by escrow PDA or by agent/depositor/nonce). This distinguishes it from sibling tools like sap_fetch_escrow (V1) and other fetch tools.

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?

Description provides context: it is read-only and should be used to inspect chain state before mutations. However, it does not explicitly mention when not to use it or provide alternatives for different escrow types.

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