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

Annotations only declare openWorldHint, so the description carries most of the burden and does add real context: 'All actions require authentication,' the reseller-only restriction on withdraw, and the distinction that fund with payment_method_id charges immediately while omitting it creates a Stripe checkout session. It does not disclose mutation reversibility, rate limits, or failure behavior across the many write actions, leaving some gaps.

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 action list is front-loaded and each parenthetical earns its place by pinning down an action's purpose, followed by the high-value fund-branch and auth sentences. There is minor formatting noise (leading whitespace) and the enumeration is dense, but overall it is efficient and well-ordered.

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 12-parameter, 9-action tool with no output schema and only openWorldHint annotations, the description covers action routing and the critical funding branch but says nothing about return values (e.g., what balance or payment-status yield) or per-action parameter requirements, which an agent must instead infer from the schema.

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 the schema already documents all 12 parameters including the charge-immediately semantics of payment_method_id, which the description merely restates. Baseline 3 applies since the description adds little parameter meaning beyond what the structured schema provides.

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 states a clear verb+resource ('Manage the wallet for the authenticated user') and enumerates all nine actions with short parentheticals, so an agent can map each action to a purpose. It is distinguishable from siblings like agent-billing and agent-subscriptions, though the wallet-vs-billing boundary is not explicitly drawn.

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?

Usage constraints are implied through the action list and one gating note ('withdraw (reseller only)'), and the fund/payment_method_id branch hints at when each funding path applies. However, there is no explicit guidance on when to choose this tool over siblings like agent-billing or agent-subscriptions, nor prerequisites for individual actions.

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