request_testnet_tokens

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

No annotations provided, but the description fully discloses the tool's behavior: automatic tUSDC opt-in for session wallet, double faucet call, rate limits, and return of optIn:true for third-party addresses. No contradictions.

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?

Description is concise (4-5 sentences) and well-structured: main action first, then conditional behavior, then limits. No redundant information.

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?

Covers most important aspects, including rate limits and behavioral nuances. Lacks full description of the response object (e.g., other fields besides optIn:true), but since no output schema exists, this is a minor gap.

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% and the description adds significant context beyond the schema, explaining the address parameter's effect on behavior (defaulting to session wallet, triggering opt-in, etc.)

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 tool's purpose: funding the active session wallet with testnet ALGO and tUSDC in one call. It distinguishes this from sibling tools like get_balance or create_wallet by focusing on testnet token acquisition.

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 explicit context on when to use (to get testnet tokens) and includes rate limits (ALGO 24h, tUSDC 1h). Differentiates behavior for active wallet vs third-party, but does not explicitly state when not to use or mention alternatives.

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