get_receipts_and_payments

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

Annotations already declare readOnlyHint=true, so no contradiction exists. The description adds useful behavioral context beyond that: the report is Tally's canned combination view, and the attempt to use the native Cash Book/Bank Book reports fails live with 'Could not find Report.' It stops short of describing response shape or pagination, but for a read-only report this is a solid disclosure.

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 first sentence is front-loaded and clear. The subsequent sentence is long and contains nested caveats, including a quoted error message, but it earns its place by preventing wasted calls to unreachable reports. It could be tightened, but the structure is still reasonably efficient.

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?

The tool has only two required date parameters, the schema fully documents them, and the read-only annotation covers safety. The description explains what the report contains, why it is the closest reachable equivalent to a Cash/Bank Book, and which sibling to use for a single ledger's history. No output schema exists, but the report's nature is sufficiently described for correct selection and invocation.

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%, with both required parameters (from, to) documented as DD-MM-YYYY dates. The description adds only that the tool works 'for a date range,' which is already implied by the schema. It provides no additional semantic detail, so the baseline 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 opens with a specific verb and resource: 'Get the Receipts and Payments report from TallyPrime for a date range.' It clearly defines the report as a cash/bank-ledger-wise view of Receipt and Payment activity, and distinguishes it from get_ledger_vouchers and the unreachable Cash/Bank Book reports. An agent can readily tell what this tool does and how it differs from nearby siblings.

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 explicitly names an alternative for single-ledger history: 'for a single cash or bank ledger's own transaction history instead, use get_ledger_vouchers with that ledger's name.' It also warns that Tally's actual Cash Book/Bank Book menu reports are not reachable via a plain Export Data request, so the agent knows when this report is the best available substitute.

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