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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, and 'Reading only' is consistent with them rather than adding new information. The description does add what the returned payload contains (available, held, spend, top-up setting), which is useful given there is no output schema, but it says nothing about permissions or scoping behavior.

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?

One front-loaded sentence with no padding; the returned-field list is informative rather than redundant. Slightly compressed punctuation-wise, but nothing needs removing.

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 zero-required-parameter read with no output schema, the description carries the return-value burden well by enumerating the balance components. The only real omission is any explanation of the version parameter.

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?

The single parameter robomart_version is an unmentioned, undocumented enum with three date-style values, and schema description coverage is 0%. The description's phrase 'this organization and environment' gestures at scoping but never explains the version parameter, so it does not compensate for the gap.

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 names a specific resource (the wallet balance for this organization and environment) and enumerates the returned fields (available, held, month spend, auto top-up setting). It doesn't compare itself to any sibling, but the sibling list is dominated by store/delivery tools that aren't plausible alternatives for a balance read.

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 only usage signal is the trailing 'Reading only.' There is no when-to-use, no when-not-to-use, and no pointer to alternatives such as request_topup for the mutation counterpart.

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