request_faucet

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

With no annotations provided, the description carries the full burden. It discloses the rate limit, the amount of USDC returned, and its purpose (enough for 2 prototype databases). It does not mention error handling or consequences of exceeding rate limits, but is adequate for a simple faucet.

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 three sentences, each serving a purpose: stating the action, providing the rate limit, and specifying the return value. There is no redundancy or irrelevant 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?

Given the tool's simplicity (one optional parameter, no output schema), the description covers the essential aspects: what it does, constraints, and expected result. It does not detail the response format, but that is less critical for a prototype 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?

The input schema has 100% coverage for the single optional parameter 'address'. The description does not add additional meaning beyond what the schema already provides ('Wallet address... If omitted, reads from local agent allowance file.'). Following the baseline rule, score is 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?

The description clearly states the action ('request'), the resource ('free testnet USDC from the Run402 faucet on Base Sepolia'), and the amount returned. It uniquely identifies the tool among siblings, as no other tool serves a similar faucet function.

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 provides explicit rate limiting (1 per IP per 24h) and the return amount, which guides usage. Although it does not mention alternatives or when not to use, the tool's single-purpose nature makes usage obvious.

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