gate_prepaid_deposit

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

No annotations provided, so description covers key behaviors: moves money, affects daily cap, supports withdrawal. Adds useful context about token matching requirement. Little missing on return value or confirmation, but overall informative.

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 sentences, no filler. First sentence states purpose and action, second explains consequences. Highly efficient.

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 2 parameters, no output schema, the description covers behavior (daily cap, withdrawal, token matching). Could mention confirmation or transaction ID, but overall sufficient for typical deposit tool.

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% with decent descriptions, but the description adds value beyond schema: clarifies token must match endpoint pricing and amount_usd is in whole units with daily cap constraint. This extra context earns above baseline 3.

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 the action 'Deposit stablecoin' into 'Solinkify pre-paid balance' and explains the purpose: to enable future gate_fetch calls to debit it without per-request fees. This distinguishes it from siblings like gate_fetch and gate_prepaid_balance.

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?

Provides context: full deposit counts against daily cap and is withdrawable, implying use for prepayment without per-request charges. Does not explicitly state when not to use, but siblings and context make alternatives clear.

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