get_groups

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=false. The description adds minimal extra behavioral context (source 'from TallyPrime') but does not disclose traits like response limits, auth requirements, or performance implications. It neither contradicts nor significantly enriches the annotations.

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 14-word sentence that front-loads the core purpose. Every word earns its place—no filler, no repetition. Highly concise and well-structured.

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?

Despite zero parameters and good annotations, the absence of an output schema means the description should explain what the returned data includes (e.g., group names, IDs, hierarchy). It does not, leaving an AI agent uncertain about the tool's output structure. For a simple list tool, some completeness 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?

With zero parameters and 100% schema coverage, the description correctly implies no input is needed. It adds no redundant parameter info. Per guidelines, zero parameters earns a baseline of 4, and the description meets that adequately.

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 'Get all account groups' with specific examples (Sundry Debtors, Fixed Assets), distinguishing it from siblings like get_ledgers or create_group. The verb+resource is explicit and 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 description implies usage when a list of account groups is needed, but provides no explicit guidance on when to avoid this tool or alternatives. With siblings like get_ledgers and get_stock_items, the context makes differentiation possible, but the description itself lacks explicit exclusions or comparative context.

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