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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieve' implies a safe read, but it never states that explicitly, nor does it mention auth requirements, whether balance is currency-denominated, or what happens on failure. For a tool with zero annotation coverage this is a substantial gap.

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?

A single front-loaded sentence with no filler or redundancy. It is lean to the point of under-specification, but nothing in it is wasted.

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?

A one-parameter read tool is a simple case, and with no output schema the description could reasonably stop early. Still, it doesn't say what a balance looks like (amount plus currency) or whether a missing wallet yields zero or an error, leaving the agent guessing at the result shape.

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% for the single parameter, so the schema already explains notification_message fully; the baseline of 3 applies. The description adds nothing about the parameter, and notably does not clarify why a wallet-balance read takes a follow-up-failure message at all, which is the one genuinely confusing element here.

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?

Specific verb 'Retrieve' plus a specific resource, 'the user's wallet balance'. It is clearly distinct from the sibling set, which is dominated by cart, order, and login tools, so confusion is unlikely. It stops short of a 5 because it says nothing about scope (per-user vs per-account, which currency) that would fully pin down the resource.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It doesn't even say whether the wallet must be set up or a login must precede the call, which matters in a sibling set that includes request_login_otp and verify_login_otp.

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