walletBalance

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

With no annotations, the description carries the burden of behavioral disclosure. 'Retrieve' signals a side-effect-free read operation, but the description does not mention return format, caching, time boundaries, or any other behavioral context beyond the basic retrieval action.

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 a single six-word sentence with no unnecessary filler. The phrase 'today's current' is slightly redundant, since 'current' already implies the present, but overall the structure is tight and front-loaded.

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-parameter read tool with no output schema, this description conveys the essential operation and expected result. It doesn't specify return formatting or exactly how 'today's' affects the value, but the tool's simplicity limits the amount of context required.

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 input schema has zero parameters and schema description coverage is 100% (an empty object), so there are no parameter details for the description to add. Per the baseline for 0-parameter tools, this is adequate.

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 uses a specific verb ('Retrieve') and a concrete resource ('today's current wallet balance'), making the tool's purpose clear. However, it does not explicitly distinguish this from siblings like walletHistory or getDashboardMetrics, and 'today's current' is mildly ambiguous.

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 implies this should be used when an agent needs the current wallet balance, but it provides no explicit guidance on when to choose this over walletHistory or other dashboard/metric tools, and it offers no exclusions or alternatives.

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