tally_delete_ledger

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds far more: the two-step preview/confirm protocol, the confirmToken return, the guarantee that nothing changes during the preview, the WRITE_REJECTED refusal semantics, and the user-approval requirement. These are exactly the behavioral traits an agent cannot infer from annotations alone.

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?

Front-loaded with the one-line purpose, then clearly labelled WHEN TO USE and WRITES TO TALLYPRIME blocks. Every sentence carries operational weight; none is filler.

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?

With no output schema, the description still explains what the call returns (a preview of the write plus a confirmToken) and how the write is ultimately committed. Combined with the failure-mode note, an agent has everything needed to call this safely.

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%, so both 'name' and 'company' are already documented in the schema, including the TALLY_COMPANY_NOT_LOADED failure mode. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 first line names a specific verb and resource ('Delete a ledger from TallyPrime') and the WHEN TO USE line scopes it to ledgers created by mistake or no longer used. It does not explicitly differentiate from nearby siblings such as tally_delete_master or tally_alter_ledger, leaving the agent to infer that a ledger is a master type.

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?

Gives an explicit when-to-use ('remove an account created by mistake or no longer used'), a when-it-will-fail condition (ledgers with posted vouchers are refused as WRITE_REJECTED), and routes the agent to the correct follow-up tool (tally_confirm_write) with an explicit prohibition on confirming unprompted.

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