request_faucet_funds

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

With no annotations, the description carries the full load and does: payout amount (3 CELO), asset restriction (no USDm/stablecoins), required CELO_MCP_FAUCET_API_KEY env var with where to get it, rate limit (10 req/24h per account and beneficiary), and return behavior. This is unusually complete for a mutation/funding tool.

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?

Six tight sentences, each carrying distinct information (scope, amount, asset limits, auth, rate limit, returns). Dense but well front-loaded; only the return-sentence runs long.

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?

No output schema exists, yet the description explains exactly what comes back (payout tx hash or request_key) and which tool to use next. Combined with auth and rate-limit disclosure, an agent has everything needed to call it correctly.

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 the schema already documents wait, network, and beneficiary. The description reinforces the network constraint and the wait-vs-request_key outcome, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Request testnet CELO from the Celo faucet') and bounds it precisely ('Testnet only (celo-sepolia); there is no mainnet faucet'). This distinguishes it cleanly from all the read-only balance/block siblings.

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 says it is testnet-only with no mainnet faucet, and names get_faucet_request_status as the follow-up path when a request_key is returned. It doesn't compare against other funding routes or state hard exclusions beyond network, but the context is clear.

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