Fetch SAP x402 Escrow

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

Adds valuable behavioral detail: 'Resolves V2 first, then V1 fallback,' which is beyond the annotations (readOnlyHint, idempotentHint). No contradiction with annotations.

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?

Relatively concise with two functional sentences and a general note about write operations. The note is slightly extraneous for this read-only tool, but the core information is front-loaded.

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?

Combined with the output schema, the description covers the main behavioral aspects (fallback, usage context). Could mention idempotency or safety, but those are covered by 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% with descriptions for all 3 parameters. The description does not add new parameter information beyond what the schema already provides, so scores at baseline.

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 action ('Fetch raw x402 escrow account data') and the SDK method used. It distinguishes from siblings by specifying the x402 namespace and raw data, but doesn't explicitly differentiate from the similar sibling sap_fetch_escrow_v2.

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?

Provides context: 'Estimate or fetch state before creating escrows or settling calls.' This implies when to use, but there are no explicit exclusions or alternatives listed, leaving the agent to infer usage boundaries.

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