botwallet_get_deposit_address

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a deposit address and a funding URL, which adds behavioral context beyond basic retrieval. However, it doesn't cover important traits like whether this is a read-only operation, if it requires authentication, rate limits, or if the address is static or dynamic per call. The description is neutral and doesn't contradict any annotations.

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 sentences that are front-loaded with the main action and resource, followed by additional context about usage and return values. Every sentence adds value: the first defines the core function, and the second explains the funding mechanism and extra output. There is no wasted text or 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?

Given the tool has no parameters, no annotations, and no output schema, the description provides basic completeness by stating what it does and what it returns. However, for a financial tool, it lacks details on security, authentication needs, or error handling, which could be important for an AI agent. It's adequate but has clear gaps in behavioral 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 has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter information, which is appropriate. Baseline is 4 for 0 parameters, as it avoids unnecessary details and focuses on the tool's purpose.

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 ('Get') and resource ('your USDC deposit address on Solana'), specifying the cryptocurrency and blockchain. It distinguishes from siblings like 'botwallet_balance' or 'botwallet_transactions' by focusing on deposit address retrieval. However, it doesn't explicitly differentiate from all possible alternatives (e.g., 'botwallet_request_funds' might also involve funding).

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 implies usage when needing a deposit address for USDC on Solana, particularly for funding the wallet. It mentions 'Anyone can send USDC to this address to fund your wallet,' suggesting a use case. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., 'botwallet_request_funds' for requesting funds from others) or any exclusions, leaving some ambiguity.

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