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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the mutation/external-effect profile is partly covered. The description adds genuinely useful behavior beyond that: the top-up-to-cap semantics, the insufficient-balance failure mode, and the returned `amountSent` delta.

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 the core action, followed by the behavioral nuance and the user-facing communication guidance. Slightly verbose in the 'Describe the behavior to the user as...' instruction, but every sentence carries actionable 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?

An output schema exists, so return values need no explanation, yet the description still points at `amountSent` as the meaningful field. Combined with the failure-mode and per-network-cap details, an agent has everything needed to call and report this tool 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 description coverage is 100% and the network enum is fully documented in the schema, including alias normalization. The description adds no additional parameter syntax or format detail, so the 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+resource combination ('Top up a testnet address from Chainstack's faucet') that no sibling tool replicates. An agent can immediately distinguish this from the node/project CRUD 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?

Explains the operational context clearly: it tops up to a per-network maximum rather than sending a fixed amount, and it fails when the address is already above the cap. It does not name alternatives or exclusions, but no sibling tool overlaps with faucet funding, so there is little to route away from.

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