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

The description asserts '(idempotent)' while the supplied annotations declare idempotentHint=false. These directly conflict on the single behavioral property that matters most for safe retry logic, so the description actively misleads rather than adding context.

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?

Two short sentences with the state transition front-loaded and the secondary parameter note following. No padding or restatement of the tool name.

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?

An output schema and annotations exist, so return values and safety profile need not be spelled out. However, the description omits what happens on an invalid state, whether partial funding is possible, and contradicts the idempotency annotation — gaps that matter for a money-moving state transition.

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 description coverage is 0%, so the description must carry the meaning. It does explain payment_ref as linking the payment-rail transaction, which is genuinely useful, but escrow_id is left completely undefined and no format or constraint is given for either parameter.

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 names a specific state transition — marking an escrow from OPEN to FUNDED — which is distinct from every sibling (open_escrow, release_escrow, refund_escrow, dispute_escrow). The verb, resource, and precondition are all present in one compact phrase.

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 precondition 'an OPEN escrow' tells the agent exactly when this tool applies, which is meaningful routing guidance within an escrow lifecycle. It stops short of explicitly naming alternatives or saying what to do when the escrow is not OPEN, so it does not reach the top band.

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