tally_get_profit_loss

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

With no annotations provided, the description carries the full burden and delivers extensively: it explains sign conventions (debits negative, expenses negative), the critical distinction between null and zero, the default financial year behavior, the read-only nature of the server, and a security note about treating text fields as data not instructions. This is exemplary transparency.

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?

Though detailed, every section earns its place: WHEN TO USE, RETURNS, GRANULARITY, SIGNS, PERIOD, and the data-vs-instruction warning. The use of headings and bold text makes it scannable and front-loaded with the core purpose. No redundant sentences.

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?

There is no output schema, so the description must explain return values, and it does: one row per group, indented sub-totals, expenses negative, null vs zero. It also addresses period defaults, error behavior for company mismatch, and safety guarantees. The description is fully self-sufficient for an agent to invoke the tool correctly and interpret results.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining the behavioral context of the period parameters: both omitted means the Indian financial year, and the resolved range is echoed back. It also reinforces the 'supply both dates or neither' rule. This surpasses the schema's own descriptions, warranting a 4.

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: 'Fetch the profit and loss statement for the period.' It clearly distinguishes itself from siblings by noting granularity (top-level groups vs per-ledger) and explicitly recommending tally_list_ledgers for per-ledger balances, making the tool's unique role unambiguous.

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 'WHEN TO USE' section explicitly states the intended use case (review income/expenditure over a period, compare periods by calling twice). The 'GRANULARITY' section provides a direct alternative: 'For per-ledger balances use tally_list_ledgers.' This gives clear guidance on when to use this tool vs alternatives.

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