getChartOfAccounts

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

The description discloses the read-only nature and the type of data returned (account categories and hierarchy). However, it does not mention authentication requirements, rate limits, or any side effects. Since no annotations are provided, the description carries full burden but covers only basic behavioral traits.

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, concise sentence (17 words) that front-loads the action and resource. Every word is necessary and contributes to understanding. No fluff or redundancy.

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?

The description covers the core functionality but lacks detail on output format or structure. Since no output schema exists, the description should ideally clarify the form of the hierarchical structure (e.g., nested JSON or flat list). It is adequate for a simple read tool but not exhaustive.

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% (the only parameter __userContext is fully described in the schema). The description adds no additional parameter information beyond what the schema provides. Per guidelines, baseline is 3 when coverage is high.

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 uses a specific verb 'Retrieve' and clearly identifies the resource as 'the chart of accounts for the organization'. It further specifies the output as 'listing all account categories and their hierarchical structure', which differentiates it from sibling tools like getAccountBalance or getBalanceSheet. The purpose is unambiguous and distinct.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools (e.g., getAccountBalance, getBalanceSheet, listAccounts), the agent lacks context on when to pick this one. No usage scenarios, prerequisites, or exclusions are mentioned.

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