erc8183_reject_job

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

The annotations already declare destructiveHint:true and openWorldHint:true, but the description adds no behavioral context beyond the word 'reject'. It does not disclose irreversibility, state transitions, or any side effects, so the description contributes nothing beyond what the annotations already provide.

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 an exceptionally concise single sentence with no filler. However, it is so minimal that it borders on under-specification, sacrificing potential clarity for brevity.

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 simple parameters and the presence of annotations, the description is minimally adequate. It lacks details about the effects of rejection, required job state, or when rejection is appropriate, which would improve completeness for an agent.

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 100% with meaningful descriptions for all three parameters: jobId, reason, and chainId. The description itself adds no parameter details, but the schema is sufficient, so the baseline score of 3 applies.

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 uses a specific verb ('Reject') and a clear resource ('ERC-8183 job'), making the action clear. It distinguishes from sibling tools like erc8183_complete_job or erc8183_submit_job by naming the rejection action, though it does not elaborate on what rejection entails.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as the job needing to be submitted, nor does it contrast rejection with completing or claiming a refund. Usage is implied only by the verb.

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