claim_faucet

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

Discloses key behavioral traits: fixed amount, per-wallet cooldown, cumulative cap, testnet context, and authentication requirement. Without annotations, this is adequate, though does not detail cooldown duration or error responses.

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, 72 words, front-loaded with core purpose, no superfluous text. Every sentence adds value.

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 simple tool with no parameters and no output schema, the description covers purpose, constraints, and differentiation from sibling. No critical gaps given the tool's complexity.

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?

No parameters exist (0 params), baseline is 4. Description confirms no arguments needed, adding clarity beyond the empty 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?

Explicitly states the action (claim), the resource (fixed testnet faucet amount of synthetic USDX), and context (authenticated account, cooldown/cap). Clearly distinguishes from sibling claim_credit by noting the fixed amount server-side.

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?

Directly compares with claim_credit, specifying that the amount is fixed and no arguments needed, guiding the agent when to choose this tool. Also mentions requirement of API credentials.

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