Get cash ledger

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

With no annotations provided, the description carries the transparency burden. It discloses a behavioral prerequisite (active taxpayer session) and 'Fetch' implies a read operation, but it does not describe return format, pagination, limits, or error behavior. This is partially transparent but not fully.

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 two short sentences with no redundancy. The action and scope are front-loaded, and the session requirement is placed second, making it easy to scan and understand.

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 simple two-parameter fetch, the description covers purpose and environment, and the schema fully documents parameters. However, there is no output schema and no mention of what the tool returns or any practical constraints, leaving some gaps in completeness.

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 description coverage is 100%; both 'from' and 'to' parameters already include format and meaning. The description adds no extra parameter-level semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific action ('Fetch'), a precise resource ('electronic cash ledger transactions'), and a scope ('for a date range'). This clearly identifies what the tool does and differentiates it from siblings like get_itc_ledger and get_ledger_balance.

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 when to use the tool: when cash ledger transactions for a date range are needed. It adds an important prerequisite ('Requires an active taxpayer session') but does not mention alternatives or scenarios where another ledger tool would be more appropriate, so guidance remains implicit rather than explicit.

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