submit_deposit

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

Discloses that the deposit moves real collateral and that it's recorded on the ledger. With no annotations, this provides necessary behavioral context. Could be clearer about testnet vs real nature, but overall good.

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?

Two efficient sentences covering purpose, difference from sibling, parameters, and behavioral note. No fluff, front-loaded with key info.

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 simple tool with 2 params, no output schema, and full schema coverage, description covers all necessary aspects: purpose, usage context, parameters, prerequisites, and side effects.

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 has 100% coverage; description only restates schema info (positive decimal, defaults to USDX). No added semantic meaning beyond 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?

Clearly states it submits a testnet/synthetic deposit via the deposits ledger, contrasts with deposit_collateral, and specifies the endpoint and effect ('moves REAL collateral'). Distinguishes itself from sibling tools.

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?

Explicitly differentiates from 'deposit_collateral' by noting deposits are recorded and listable. Mentions requirement for API credentials, guiding when the tool is appropriate.

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