erc8183_fund_job

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

Annotations already flag destructiveHint=true, but the description adds meaningful side-effect context: it will perform an allowance check and possibly execute an approve transaction before funding, all in a single confirmation flow. This goes beyond the annotation's general danger flag and helps the agent anticipate the sequence of on-chain actions.

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 two sentences long and front-loaded with the core purpose. It wastes no words and efficiently conveys both the action and the internal flow. Every sentence earns its place.

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 write tool with no output schema, the description adequately captures what it does, the side-effect (approve), and the confirmation requirement. It does not explicitly state return values, but that is not required without an output schema. The surrounding sibling tools provide lifecycle context, making the description sufficiently complete for selection.

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 descriptions for all three parameters (jobId, chainId, expectedBudget) with 100% coverage, so the baseline is 3. The tool description itself adds no parameter-specific meaning; it only says 'expected budget amount in token smallest units' in the schema, which is sufficient but minimal. No extra semantic value from the description.

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 tool's function with a specific verb and resource: 'Fund ERC-8183 job escrow.' It further distinguishes it from sibling tools by detailing the internal flow (allowance check + approve if needed, then fund), which uniquely identifies this as the funding operation in the ERC-8183 lifecycle.

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 implies the tool is the funding step in an escrow job lifecycle and mentions the allowance/approve flow, giving context for when to use it. However, it does not explicitly name alternatives or say when not to use it, though the sibling tool names (e.g., erc8183_create_job, erc8183_set_budget) provide enough distinction.

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