get_chart_of_accounts_report

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

No annotations are provided, so the description must disclose behavioral traits. It includes column naming details and the general functionality, but does not mention safety (e.g., read-only), performance, or any side effects. As a report tool, destructive behavior is unlikely, but the description could add more context like that it is read-only.

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 concise with two sentences and no extraneous details. It front-loads the core purpose and follows with important column naming caveats. Every sentence serves a clear function.

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 the tool has one optional parameter and no output schema, the description adequately explains what is returned (chart of accounts with GL account information) and how to use columns. It does not explain return structure, but the use case is straightforward. The description is complete for the complexity level.

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 coverage is 100% with one parameter fully described. The description adds value by emphasizing the lookup-specific columns ('number', 'account_name', 'gl_account_id'), which goes beyond the schema's enum list. This helps an agent understand the purpose behind the columns.

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 explicitly states it returns the chart of accounts with GL account information and specifies its use for looking up gl_account_ids by number or name. This clearly indicates the tool's verb (returns) and resource (chart of accounts), and the lookup purpose distinguishes it from sibling report tools.

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 clear usage context by stating when to use the tool (to lookup gl_account_ids by GL account number or name). It does not explicitly state when not to use it or list alternatives, but the sibling context shows many other reports, so the guidance is sufficient for appropriate selection.

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