Scaffold deposit calldata

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns unsigned calldata only, implies no on-chain execution, and warns about prototype quality. This is meaningful context beyond what the tool name or schema conveys.

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?

Three short sentences with no filler. The critical prototype warning is front-loaded, followed by what the tool returns and the intended workflow. Every sentence adds value.

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 single-parameter scaffold tool with no output schema, the description covers the essential safety, output type, and workflow. It does not spell out the return encoding or deposit target specifics, but those are reasonably inferable from the tool name and sibling 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 description coverage is 100%, and the schema already fully explains 'amount' as USDC native units in integer string form with 6 decimals. The main description adds no further parameter meaning, so the baseline score of 3 applies.

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 clear verb and resource: 'Returns unsigned approve+deposit calldata.' This distinguishes it from siblings like build_order_tx, which handles orders, and from the various get_* tools. The prototype warning further narrows its identity.

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?

It gives clear contextual guidance: 'PROTOTYPE ONLY', 'Simulate, then sign locally', and 'Not for production bots.' This tells an agent when it is acceptable to use the tool, though it stops short of explicitly naming alternative tools or exact conditions for choosing a different one.

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