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

Goes well beyond the annotations: it discloses that the amount is computed as a delta to a per-network cap, names the specific failure mode (insufficient-balance), documents the 429 cooldown behavior with scope (per organization, per address, per network) and that the error carries the next-available time. It also pre-empts a false-retry pitfall by stating a success is final even if the balance hasn't refreshed, which is behavior the structured fields cannot express.

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?

Front-loaded with purpose, then failures, then cooldown, then retry guidance — a sensible order with no filler. It is longer than average and includes agent-directed phrasing advice ("describe as top up not give"), which is useful but borders on verbose for a two-parameter tool.

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 everything an agent needs to call and interpret this tool correctly: cap semantics, refusal conditions, cooldown scope, and retry behavior. Return values are backed by an output schema, and the description still points at `amountSent` and `transaction` for the cases where interpretation matters.

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 address format and network enum are already well documented. The description adds meaning the schema does not: the per-network maximum concept tied to `network` (e.g. 0.5 ETH on sepolia) and the returned `amountSent` delta, which explains what the inputs actually produce.

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?

Opens with a specific verb+resource ("Top up a testnet address from Chainstack's faucet") and immediately clarifies the non-obvious semantics that the amount is a top-up-to-cap, not a fixed payout. No sibling tool does faucet funding, so it is unambiguous against the listed alternatives.

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?

Clearly frames the use case (funding testnet addresses) and the conditions under which the call is refused: address already above cap, or a repeat within the 24-hour per-network cooldown. It does not name alternatives or say explicitly when not to use it in favor of another tool, but the constraint context is strong enough that an agent knows when this applies.

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