release_escrow

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

With no annotations, the description must disclose behavioral implications. It mentions poster-only and automatic-by-default, but omits consequences of releasing escrow (funds transfer, irreversibility, failure conditions), which is critical for a financial mutation.

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?

Single concise sentence with all key information front-loaded; no filler or redundant wording.

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?

Low parameter complexity keeps it simple, but as a financial action it lacks side-effect/eligibility detail and error information, making it only minimally 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?

Schema provides only a string jobId with no description. The tool description adds that the job must be completed, giving meaningful semantic context to the parameter, though it doesn't specify format or additional validation.

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 action ('release escrow'), target ('completed job'), and role constraint ('poster only'), distinguishing it from related job actions like approve_work or accept_bid.

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?

It conveys when to use the tool (manual release on a completed job) and the poster-only restriction, but does not explicitly name alternatives or exclusions. The 'normally automatic' hint adds context for exceptional manual use.

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