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

Annotations are all false and offer no behavioral safety signal, so the description carries that burden. It discloses several non-obvious behaviors: Plaza locks funds, verifies work, charges a 5% fee, requires a $50 minimum, has a 24-hour dispute window, and jobs can never be deleted. Per-action side effects are not detailed, but the transparency is well above baseline.

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 compact and information-dense, placing the action list near the start and then delivering key constraints in short clauses. The opening tagline 'The autonomous gig economy' is mildly promotional, but the overall structure wastes little space.

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?

This is a multi-action stateful tool with 10 parameters and no per-action required-parameter mapping-executing fund, release, dispute, and status likely have very different requirements. The description lacks the operational detail needed to invoke actions correctly, and the output schema does not resolve which parameters are required for each action.

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 only 20%, and the description does not compensate for the nine undocumented parameters. It repeats the action enum but does not explain the roles of jobId, wallet, evidence, amountUsd, deliverable, paymentProof, or workerWallet. An agent would still need to guess which parameters apply to which action.

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 clear domain ('autonomous gig economy') and enumerates the exact actions the tool performs: create, fund, submit, release, dispute, status, board. It is clear that this is a versatile escrow tool, though it does not explicitly differentiate itself from the sibling tool escrow.verify_work.

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 gives no direct guidance on when to choose this tool over alternatives like escrow.verify_work or plaza.* tools. It provides context about fees and limits but no explicit 'use this when...' or exclusion criteria, leaving usage decisions to inference.

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