tally_get_gst_transactions

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explicitly states that no calculation is performed, data is returned verbatim, the empty-result case is a valid answer, and warns that text fields are data not instructions. It also declares the server as strictly read-only, covering non-obvious safety and integrity traits.

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 long but effectively structured with clear section headers (WHEN TO USE, RETURNS, DERIVED FROM, NOTHING IS CALCULATED, IF EMPTY, PERIOD). Every sentence contributes meaningful operational or safety context, and the most important information is front-loaded. The length is justified by the complexity and potential misuse of GST data.

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 tool with no output schema and no annotations, the description covers all essential aspects: what it returns (one row per voucher with verbatim GST fields), its derivation, edge cases (empty results, company configuration), period behavior, and critical non-calculations. It also distinguishes from related tools, making it self-sufficient for an agent.

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 schema already documents all 5 parameters with descriptive details, achieving 100% coverage, so the baseline is 3. The description adds little extra parametric meaning; its period note ('both dates or neither; omitted means the financial year containing today') essentially restates what the schema already says for fromDate/toDate.

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 opening line clearly states what the tool does: it returns 'Transactions carrying GST detail in a period, with the GST fields TallyPrime recorded on each.' It further differentiates from siblings by explicitly noting 'NOTHING IS CALCULATED' and 'Not a GST return report,' making its scope and distinction from tally_get_gst_summary evident.

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 provides a dedicated 'WHEN TO USE' section: to examine how GST was recorded on specific transactions 'as entered rather than as computed.' It also gives clear exclusion guidance (do not use for GST liability calculation), explains how to handle empty results by checking tally_get_company, and specifies period semantics ('both dates or neither').

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