sap_x402_build_headers_from_escrow

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

The description mentions 'fetching escrow data', indicating a read operation, but does not disclose other behavioral traits such as authorization requirements, idempotency, or potential side effects. With no annotations, the description provides minimal transparency beyond the basic action.

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?

A single, front-loaded sentence clearly communicates the tool's purpose and method. No extraneous information is included, making it highly concise.

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?

The tool is simple with two optional parameters and no output schema. The description adequately explains what the tool does but does not elaborate on the return format or provide any error context. It is minimally complete.

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%, and the description adds no additional meaning beyond what the input schema already provides for both 'network' and 'agentWallet'. The baseline of 3 applies as per guidelines.

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 tool builds SAP x402 HTTP headers by fetching escrow data for an agent wallet, mentioning the SDK method. The name and description implicitly distinguish it from the sibling 'sap_x402_build_payment_headers' by specifying 'from escrow'.

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?

No guidance is provided on when to use this tool versus alternatives like 'sap_x402_build_payment_headers'. There is no mention of prerequisites, conditions, or exclusions, leaving the agent to infer usage solely from the name and description.

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