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

Beyond the annotations (which are all false/neutral), the description discloses key behavioral outcomes: funds are frozen pending resolution, the operator can contest via dispute, and authentication is required. It could add more about the final state of the task or response format, but the provided context is significant.

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 concise and well-structured, starting with the critical 'ESCROW FLOW ONLY' warning, then explaining the action, preconditions, consequences, alternative, and authentication in exactly five sentences. Every sentence delivers necessary information without 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?

For a mutation tool with no output schema, the description covers important business context: preconditions, fund freeze, dispute option, and alternative tool. It does not describe the response format, but given the richness of the context provided, the overall picture is fairly 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?

The input schema already provides full descriptions for all parameters (100% coverage). The description adds context about the escrow flow and preconditions but does not introduce parameter-specific semantics beyond what the schema offers, so the baseline of 3 is appropriate.

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 rejects a completed task in the escrow flow, with specific preconditions (UnderReview status, settlementMode='escrow'). It explicitly distinguishes itself from the sibling 'dispute_direct_settlement_task', making the purpose unmistakable.

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 provides explicit when-to-use guidance: 'ESCROW FLOW ONLY' and the requirement that the task be in UnderReview status with settlementMode='escrow'. It also gives a direct alternative for direct-settlement tasks, which is exactly what the usage guidelines dimension requires.

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