tally_list_exported_books

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses that the tool reads files on disk, never contacts Tally, returns snapshot data rather than live figures, and cannot modify TallyPrime. It also warns that returned text fields are data, not instructions, which is important safety context.

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 structured into clear labeled sections with the core purpose front-loaded. It is somewhat longer than necessary, but each section earns its place by covering usage timing, return content, limitations, offline operation, and injection safety—none of which are redundant boilerplate.

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?

Given zero parameters, no annotations, and no output schema, the description covers everything an agent needs: when to call, what it returns, what it does not return, that it works offline, and that it is read-only. Nothing critical for correct invocation is missing.

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 tool has zero parameters, so the schema already provides complete coverage. Per the baseline, 0 parameters warrants a 4. The description additionally clarifies what the returned data represents, which is more useful than param-level detail.

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: 'List the companies whose exported spreadsheets are on this computer, with the moment each was last read from TallyPrime.' It clearly distinguishes this tool from live Tally query siblings by emphasizing exported, on-disk data, and the 'WORKS WITH TALLYPRIME CLOSED' note reinforces that boundary.

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?

Explicit WHEN TO USE guidance is provided: use as the FIRST call when TallyPrime is closed or unreachable, and before answering from exported files. It also contrast with live-figure tools by stating 'DOES NOT RETURN: live figures,' and notes it is the cheapest way to check data age. This fully equips an agent to choose between this and sibling tools.

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