list_groups

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

With no annotations provided, the description carries the full burden. The word 'Returns' implies a read-only operation and 'all' indicates full scope, but it does not disclose authentication needs, company scope, or output format. This is sufficient for a simple list tool but lacks detailed behavioral 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 a single sentence that is front-loaded with the main action ('Returns all accounting groups') and enriched by relevant examples. Every word earns its place with no redundancy or 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?

For a zero-parameter, no-output-schema tool, the description adequately defines what is returned and provides illustrative examples. It is slightly incomplete in not clarifying whether results are scoped to a specific company or describing the return shape, but overall it gives enough context for a simple list tool.

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, and schema coverage is 100% (empty schema). Per guidelines, the baseline for 0 parameters is 4. The description adds no parameter-specific semantics, but none are needed.

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 clearly states the tool 'Returns all accounting groups (chart-of-accounts categories) from TallyPrime' and gives concrete examples like 'Sundry Debtors, Bank Accounts, Direct Expenses'. This specific verb+resource combination distinguishes it from sibling list tools such as list_ledgers and list_companies.

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 implies when to use the tool (when you need accounting groups) but does not explicitly discuss alternatives or exclusion criteria. Unlike the high benchmark, it does not mention 'use list_ledgers for ledgers' or similar, leaving usage guidance to inference.

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