pro_deposit

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

Without annotations, the description should disclose behavioral traits. It states 'Transfer is immediate' and explains status enum, but does not mention authentication requirements (despite optional jwt parameter), rate limits, or handling of insufficient funds. The '[PRIVATE]' tag is ambiguous. Some gaps remain.

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?

Very concise: 4 sentences, front-loaded with purpose, then workflow steps. No unnecessary words or repetition.

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?

Completes the picture for a simple transfer: prerequisite, immediate action, status enum, verification step. No output schema needed. The presence of a privacy tag adds relevant 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 coverage is 100%, so baseline is 3. The description adds context about the simple wallet requirement but does not elaborate on individual parameters beyond what the schema provides.

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 'Deposit funds from Simple Wallet to Pro Trading account.' The verb 'deposit' with specific source and destination distinguishes it from sibling tools like 'pro_withdraw' and 'earn_deposit'.

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 instructs: funds must be available in Simple Wallet first (check with wallet_get_pockets), and recommends verifying with pro_get_balance. Also explains the transfer status ENUM, guiding the agent on expected outcomes.

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