sap_settle_escrow

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

With no annotations, the description must disclose behavioral traits but fails to do so. It does not indicate whether the tool is read-only or destructive, what changes occur (e.g., escrow state transitions), or any side effects like fee deductions. Only minimal intent is conveyed.

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, front-loaded sentence that efficiently states the core action. However, it sacrifices necessary detail for brevity, making it somewhat insufficient. It earns points for conciseness but loses due to incompleteness.

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 lack of annotations, output schema, and the domain-specific nature (SAP V1 escrow), the description is insufficient. It does not explain the return value, error conditions, or any required context like escrow existence or call recording, leaving significant gaps for a safe agent invocation.

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?

The input schema provides 100% coverage with clear descriptions for each parameter. The description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance understanding of parameter usage or constraints.

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 uses the verb 'Settle' and specifies the resource 'calls against a V1 escrow', which distinguishes it from V2 and batch variants among siblings. However, it lacks explanation of what 'settle calls' means in the context of the SAP protocol, leaving some ambiguity.

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_settle_escrow_batch or sap_settle_escrow_v2. There is no mention of prerequisites, such as requiring a valid escrow or previously recorded calls, which limits the agent's ability to decide correctly.

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