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

Description discloses that the tool syncs with the payment provider and automatically funds the task if sufficient balance exists, adding behavioral detail beyond annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false). It also notes authentication requirement, though that's implied by the apiKey parameter.

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?

Four sentences, each serving a purpose: warning, function, usage context, and authentication/sync behavior. No filler or redundancy.

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 description covers purpose, scope, usage timing, and side effects comprehensively for a moderate-complexity tool. However, with no output schema, it fails to describe the return value or error conditions (e.g., what happens when no payment is received), which is a minor gap.

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 already fully describes both parameters (apiKey and taskId) with 100% coverage. The description does not add additional parameter-specific semantics beyond the schema, so baseline score applies.

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 checks for PSP payment and funds the task, explicitly scoping to escrow flow and excluding direct-settlement tasks. This specific verb-resource pairing distinguishes it from sibling tools like fund_task and acknowledge_direct_settlement_task.

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 explicit when-to-use guidance: only for quoted escrow tasks after payment via checkout URL or bank transfer, and explicitly warns not to call on settlementMode='direct' tasks. This gives clear context for tool selection without naming alternatives but by exclusion.

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