balance

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

Discloses authentication requirement with '[REQUIRES AUTH]' and the filtering behavior 'non-zero only'. No annotations provided, so the description carries the full burden. Additional details like rate limits or response format are missing but acceptable for a simple tool.

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?

Extremely concise at 6 words, front-loaded with authentication requirement. Every word is necessary and informative.

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 tool with no output schema, the description is minimally adequate but lacks context on what 'wallet' means, whether it returns balances for all wallets or the default, and how to interpret the response. Could be more complete given the sibling complexity.

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?

No parameters exist, so schema coverage is 100%. Baseline is 4 per rules. The description adds no parameter info but the filter 'non-zero only' is behavioral rather than semantic.

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?

Description clearly states 'Get wallet balances (non-zero only)', specifying the verb and resource with a filter. However, it does not explicitly differentiate from the sibling tool 'account_info' which may also provide balance information.

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?

No guidance on when to use this tool versus alternatives like 'paper_balance' or 'account_info'. The description lacks when-to-use or when-not-to-use advice.

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