create_ledger

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

No annotations are provided, so the description carries the full burden. It never states that this writes to Tally, that a backup is taken, that dry_run exists for previewing the XML, or that raw XML can be injected via extra_xml — all of which are behavioral traits an agent must know before a mutation call.

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?

A single front-loaded sentence with zero waste, so nothing needs trimming. But the brevity reads as under-specification rather than discipline given the tool's 23-parameter surface.

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?

A 23-parameter mutation tool with no annotations and no output schema gets one sentence of description. An agent has no way to know the write semantics, the dry-run option, or how the many optional fields behave — this is materially incomplete.

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 only 35% across 23 parameters, so the description must compensate, and it does not. The parenthetical hints implicitly at the required 'group' value space, but nothing is said about opening_balance/opening_type, GST fields, credit_days, or the dry_run preview path.

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?

States a specific verb+resource ('Create a ledger') and the parenthetical examples (party, bank, expense, income, tax) clarify what a ledger group looks like, which is genuinely useful. It does not, however, distinguish this from create_master or alter_ledger, so an agent cannot route between them from the description alone.

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?

No guidance on when to use this versus alter_ledger (existing ledger) or create_master (generic master creation), both of which are siblings. No prerequisites, no mention of the company context needed to target the right Tally instance.

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