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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered by structured data. The description adds real value beyond that: the charge hits the owner's card, is bounded by 'the owner's configured limits', and the result differs depending on mandate presence. It stops short of warning that repeated calls trigger repeated charges or what happens on a declined/over-limit card.

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?

Three short sentences, front-loaded with the charge action and its funding source. Every sentence carries distinct information (mandate path, limits, no-mandate fallback) with no repetition or 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 single-optional-param money-mutating tool with no output schema, the description covers outcomes on both branches (new balance vs payment instructions) and the charge bounding. It lacks explicit idempotency/repeat-charge guidance and failure handling, though annotations partly cover the mutation semantics.

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%, and the schema itself documents the default-to-mandate-amount and clamping behavior, so the description needs to add little. The description alludes to 'configured limits' and the mandate's refill amount but never mentions the amount_usd parameter directly. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Top up the apifare balance') and immediately names the funding mechanism (the owner's standing auto-refill mandate). This is clearly distinguishable from the sibling check_balance (a read) and call_api (a spend per call), so an agent can tell them apart without opening a 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?

Gives the condition that selects the charging path ('if the owner enabled one') and the fallback behavior ('Without a mandate, returns payment instructions to relay to the user'). It does not explicitly route to alternatives such as check_balance or state when-not-to-use, but the conditional context is clear.

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