show_balance

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

Describes return structure (type, sub_type, category, amount, date) and behavior with period. However, no annotations exist, and the description does not explicitly state this is a read-only operation, though implied by 'show'.

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?

Three sentences, each serving a purpose: purpose, structure, and usage guidance. No wasted words, front-loaded with key information.

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?

Covers purpose, parameters, return structure, and usage modes. Lacks explicit read-only declaration and pagination details, but sufficient for a simple listing tool given no output 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 coverage is 100%, but the description adds value by explaining the optionality of 'period' (all vs. snapshot) and listing currencies for 'display_currency' beyond the schema's short description.

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?

Clearly states the tool retrieves balance sheet entries (assets + liabilities) by period. Distinguishes itself from sibling 'show_' tools by specifying the data type (balance sheet) and behavior with/without period.

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?

Explicitly explains when to use without period (trends) and with period (snapshot). Does not mention exclusions or alternatives, but the guidance is clear for common use cases.

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