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

Annotations already establish that the operation is mutating (readOnlyHint=false), has external side effects (openWorldHint=true), and is non-idempotent. The description adds the useful cost signal ($5.00 USDC) and the target network, but it does not mention irreversibility, wallet funding requirements, or other on-chain consequences. With annotation coverage, this is adequate but not rich.

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 front-loaded sentence with no filler. It efficiently communicates the operation, contract types, network, and price, which is ideal for a tool with only one parameter.

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?

The tool is simple: one required enum parameter, and an output schema exists. The description covers the key context of network and cost. However, the invalid contract-type wording introduces ambiguity, and deployment prerequisites (wallet, USDC balance, gas) are not mentioned. It is sufficient for a low-complexity tool but has clear gaps.

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% and the enum is self-documenting, so the baseline would be 3. However, the description says 'escrow, bounty, or agent' while the schema enum allows 'escrow', 'bounty', and 'subscription'. This is actively misleading: an agent could submit the invalid value 'agent' and never know 'subscription' exists. The description undermines, rather than adds to, the schema semantics.

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 states a specific verb ('deploys'), a concrete resource ('custom escrow, bounty, or agent smart contracts'), and a target chain ('Arc Mainnet'), plus a price. This is clearly distinguishable from the sibling deploy_contract and deploy_solana_contract tools by network and contract domain. The minor wording mismatch with the schema enum does not obscure the core purpose.

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 target network and contract types imply when the tool is appropriate, and the description names a concrete domain (escrow/bounty/agent). However, it never explicitly says 'use this for Arc Mainnet' or contrasts with the generic deploy_contract or deploy_solana_contract siblings, leaving selection partially to inference.

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