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

Annotations already declare destructiveHint=true and non-idempotent behavior, so the description needn't repeat those. It adds valuable context beyond annotations: the required api_key, the source of funds for paper vs live clones, and that real USDC never moves for paper clones. It still does not describe success/failure outcomes or confirmation behavior.

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?

Front-loads the action and prerequisite, then immediately covers the paper/live distinction and REST equivalent. It is dense but every clause adds useful information, with no filler.

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?

Covers auth, funding source, clone-type behavior, and the REST twin for a destructive mutation. With no output schema, it could say more about the expected response or failure modes, but it is largely complete for calling the tool correctly.

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%, so the baseline is 3. The description adds meaningful semantics by explaining that the amount is drawn from simulated balance for paper clones and real internal USDC for live clones, which goes beyond the schema's simple 'USDC amount to transfer' definition.

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?

States a specific verb and resource: 'Move USDC into one of YOUR clones' isolated bot balance.' It further distinguishes the paper-clone vs live-clone funding semantics and gives the REST twin endpoint. An agent can identify the action without opening the schema.

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?

Explains the prerequisite api_key and how funding differs for PAPER vs LIVE clones, which is clear contextual guidance. It does not name alternative tools or explicit when-not conditions, but no close sibling appears to offer the same funding action.

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