Get cash + ITC balance

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

With no annotations, the description carries the full burden. It discloses one meaningful behavioral prerequisite ('Requires an active taxpayer session') and the verb 'Fetch' implies a read operation, but it does not describe the return format, failure modes, or consequences of an expired session.

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?

Two short sentences front-load the core operation and follow with the session prerequisite. There is no filler or redundant repetition of the title.

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 low-complexity two-parameter lookup, the description covers the purpose, the required period, and the key precondition. It leaves the sibling distinction and exact return shape implicit, but nothing essential to attempting the call is missing.

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 already provides 100% coverage with format rules and examples for both year and month. The description only echoes 'return period (year/month)' and adds no meaningful semantic value beyond the schema.

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 ('Fetch') and identifies a clear resource ('Cash and ITC ledger balances') with a temporal scope ('as on a return period'). It does not explicitly contrast with sibling tools like get_cash_ledger or get_itc_ledger, but the combined balance view is reasonably distinguishable.

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 is provided for when to use this tool versus alternatives such as get_cash_ledger or get_itc_ledger. The active-session note addresses a prerequisite but does not help an agent choose between this and sibling tools.

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