erc8183_complete_job

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

Annotations already declare destructiveHint and openWorldHint, indicating this is a potentially destructive operation. The description adds the specific consequence 'release escrow', which is useful context beyond the annotations. However, it does not disclose irreversibility, state requirements, or return behavior, so the additional transparency is limited.

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 a single concise sentence, front-loaded with the verb 'Complete' and the resource, with no redundant or filler content. It immediately conveys the core purpose and effect.

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?

Given the tool's mutation nature, the annotations provide safety context (destructiveHint), and the schema is fully documented. The description covers the core action and immediate effect ('release escrow'). However, it lacks information about when the job can be completed (e.g., required prior states), which might be important for correct invocation, making it minimally sufficient rather than thorough.

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 provides 100% coverage for all parameters (jobId, reason, chainId) with clear descriptions. The tool description does not add any parameter-specific semantics beyond what the schema already contains, so it neither enhances nor detracts from the schema information.

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 ('Complete') and the resource ('an ERC-8183 job'), with a specific outcome ('release escrow'). It distinguishes from sibling tools like erc8183_submit_job and erc8183_reject_job by using 'complete' as the verb.

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 action of 'complete' implies it is used to finalize a job after it has been submitted, but the description does not explicitly state when to use it versus alternatives like erc8183_submit_job or erc8183_reject_job. No exclusions or prerequisites are mentioned, leaving usage context partly implicit.

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