get_faucet_request_status

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the key trait that this is an asynchronous status check that returns a payout transaction hash once the status is Done, but it never names the other possible statuses (pending, failed), whether the call is safe to repeat, or what is returned before completion.

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, front-loaded with the purpose and then the return value. Every clause earns its place with no filler.

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 two-parameter read tool with no output schema, the description covers purpose, input origin, and the primary return value. The gap is the absence of the full status vocabulary an agent needs to interpret a non-Done result.

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 description coverage is 100%, so both parameters (request_key and the network enum defaulting to celo-sepolia) are already fully documented. The description restates that request_key comes from request_faucet_funds, which is already in the schema, and says nothing about the network parameter.

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+resource (check whether a queued faucet request has paid out) and clearly distinguishes itself from the sibling request_faucet_funds, which creates the request while this one polls its outcome. An agent can pick between the two without opening either schema.

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 ties the call to request_faucet_funds by naming the request_key as the argument, which implies the correct sequence (request, then check status). It doesn't state explicit exclusions or what to do if the status never reaches Done, but the usage context is clear.

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