get_ledger

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

With no annotations, the description carries the burden of behavioral disclosure. It adds some useful context such as 'Exact ledger name as it appears in TallyPrime' and 'If omitted, uses the configured default' for company, but it does not describe behaviors like whether from/to dates form an inclusive range or what happens when dates are omitted.

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 compact and well-structured: a one-sentence summary followed by a clear Args list with no filler. Every line adds needed parameter detail, and the most important scoping information is front-loaded.

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 read-oriented tool with an output schema, the description covers the essential invocation details: exact ledger name, company fallback, and date formats. The only notable gap is ambiguity around whether both date bounds are needed together)Skip, but the individual optional markers and the output schema mitigate this.

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 0%, so the description must compensate. It does by giving each parameter meaningful guidance: exact ledger name, company default behavior, and ISO format for optional dates. This adds real value beyond the bare schema types and defaults.

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 names a specific verb and resource: 'Get a ledger's master details plus its transactions (vouchers) in a date range.' This clearly distinguishes it from siblings like get_voucher and search_vouchers by emphasizing the ledger-level aggregation and date-range scoping.

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 explains required inputs but gives no explicit guidance on when to choose this tool over alternatives. It does not mention that search_vouchers should be used for voucher-level search, or that list_ledgers lists available ledgers, leaving usage routing to inference.

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