sap_x402_fetch_escrow

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

With no annotations, the description must fully disclose behavioral traits. It states 'Fetch' which implies read-only, but does not explicitly confirm non-modification, required permissions, or behavior when data is missing. The low score reflects this gap.

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 two sentences and 20 words, efficiently conveying the core action and fallback behavior. Every word is necessary, making it optimally 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?

Lacking an output schema, the description does not hint at the structure of 'raw x402 escrow account data' or what fields are returned, leaving the agent without essential context for interpreting results.

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 the baseline is 3. The description does not add any extra meaning beyond what the schema already provides for the two parameters, falling short of adding value.

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 explicitly states the tool fetches raw x402 escrow account data, using a specific SDK method. It distinguishes itself from sibling tools like sap_fetch_escrow and sap_fetch_escrow_v2 by specifying 'x402' and mentioning the V2/V1 resolution fallback.

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 implies usage for x402 escrow data but does not explicitly state when to use this tool versus alternatives. The fallback behavior is mentioned, but no direct comparison with siblings or exclusionary guidance is provided.

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