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

Annotations already indicate readOnlyHint=false, openWorldHint=true, and idempotentHint=false, covering the safety profile. The description adds the cost of deployment ($5.00 USDC) and the target network, which are useful behavioral details. However, it doesn't disclose any side effects, authorization requirements, or what happens on success/failure, so the added value is moderate.

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 that front-loads the action and includes key details (network, cost, contract types). It is efficient with words, though it could be slightly more structured by explicitly listing all enum values. Overall, it's well-sized and to the point.

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 this is a deployment tool with side effects, the description provides the network and cost but omits details like prerequisites (e.g., funded wallet), deployment process, or post-deployment artifacts. The presence of an output schema helps, but for an action that modifies state, more context about expected behavior and potential failures would improve completeness.

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%, so the schema already documents the single parameter (contractType) and its enum values. The description lists some of the types (escrow, bounty, agent) but doesn't explain the meaning or trade-offs of each, and it introduces 'agent' which isn't in the enum. The description adds minimal semantic value beyond the schema.

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 verb 'Deploys' and the resource 'smart contracts', and specifies the network (Base Mainnet) and cost ($5.00 USDC). It names three contract types (escrow, bounty, agent), but the schema enum includes 'subscription' and 'pendle' which are omitted, and 'agent' is not an enum value. It does not differentiate from sibling deployment tools like deploy_arc_contract or deploy_solana_contract, but the purpose is still clear enough.

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 the other deployment siblings (deploy_arc_contract, deploy_solana_contract). The description doesn't mention any conditions, prerequisites, or alternatives, leaving the agent to infer usage from context alone.

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