deposit_collateral

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

The phrase 'This moves REAL collateral on the account' discloses a critical behavioral trait (irreversible action). However, with no annotations provided, the description could further clarify side effects, error conditions, or confirmation steps.

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 two concise sentences, front-loaded with the action and followed by essential parameter guidance and a behavioral note. Every sentence adds value without redundancy.

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 mutation tool with no output schema, the description covers the basic purpose and a key behavioral trait. However, it lacks information about return values, error handling, or post-action state, leaving the agent with incomplete 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?

The input schema covers 100% of the parameter, and the description merely restates what the schema already says (amount is a positive decimal string). No additional semantic context is provided 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 action ('deposit USDX collateral') and the target ('authenticated account'). However, it does not distinguish from the sibling tool 'submit_deposit', which may cause confusion about the specific step.

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 description mentions 'requires API credentials' but does not provide guidance on when to use this tool versus alternatives like 'submit_deposit' or 'claim_faucet'. No when-not-to-use or prerequisites are specified.

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