erc8183_submit_job

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

Annotations already declare destructiveHint and openWorldHint, indicating a state-changing operation. The description adds no additional behavioral context—it does not disclose that submitting the deliverable hash is likely an irreversible on-chain transaction or mention any authorization requirements. No contradiction exists, but the description contributes nothing beyond the annotations.

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, tightly worded sentence that immediately states the core action. It is front-loaded and contains no unnecessary words, exemplifying conciseness even if slightly under-specified.

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 destructive operation with no output schema, the description is minimal. It omits essential context: whether this involves an on-chain transaction, how it fits into the ERC-8183 lifecycle (after creation/funding, before completion), and potential side effects. The schema clarifies parameters but not the operational context.

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 coverage is 100%, with every parameter described, including the key detail that the 'deliverable' string is keccak256 hashed. The tool description adds no extra parameter semantics beyond the schema, 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 action (submit) and resource (job deliverable hash) within the ERC-8183 context, distinguishing it from siblings like erc8183_create_job or erc8183_complete_job. It lacks explicit detail about the hashing behavior but is specific enough for basic tool selection.

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?

No guidance is provided on when to use this tool versus alternatives in the ERC-8183 workflow. The description does not mention prerequisites (e.g., job creation, funding) or indicate that it should precede completion or rejection steps, leaving the agent to infer the sequence.

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