Set auto-reload

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

Annotations indicate idempotentHint=true, destructiveHint=false. Description adds useful behavioral context: server-side operation, requires saved card, provides error guidance. However, it doesn't detail potential side effects like card charging timing or limitations.

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?

The description is detailed yet concise, front-loading the core action. Some conditional details (card setup, member message) add length but are justified. No wasted sentences.

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?

Given the tool's complexity (admin-only, card dependency, server-side), the description covers prerequisites, error handling, role restrictions, and references related tools. An output schema exists but isn't needed per rules.

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?

Input schema has 100% coverage and descriptions. The description adds value by specifying reloadCredits must match a credit pack size (referencing buy_credits), but otherwise reinforces schema details without major new meaning.

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?

The description clearly states the tool turns automatic credit reloads on or off, including the mechanism (threshold, top-up) and that it's admin-only. It effectively distinguishes from siblings like buy_credits by detailing the server-side, card-on-file process.

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 states when to use: admin only, requires a saved card. Gives instructions if no card saved and mentions members get an 'ask an admin' message, providing clear usage boundaries.

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