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

readOnlyHint=true already declares this a safe read, so the description only needs to add context; the GET /charts endpoint reference is a small addition. It says nothing about pagination, result ordering, or whether the chart is hierarchical, which are the traits an agent would actually want beyond the annotation.

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?

Three short sentences, front-loaded with the purpose, then the optional filter, then the endpoint. The endpoint line is marginal for invocation but useful for debugging; nothing else is wasted.

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 one-parameter read tool with readOnlyHint and full schema coverage, the essentials are present. With no output schema, though, the description never indicates what an account record contains or how many come back, leaving a real gap for result handling.

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% and the single optional parameter is documented there, so the baseline of 3 applies. The description restates the filter's purpose but adds no allowed values, case sensitivity, or behavior when the filter is omitted.

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?

States a specific verb and resource ("List the chart of accounts"), which is unambiguous against siblings like list_customers or list_invoices. It does not, however, explicitly differentiate itself from trial_balance, the other accounting-structure sibling.

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?

"Optionally filter by account type" hints at one usage pattern but gives no when-to-use criteria, no prerequisites, and no pointer to alternatives such as runmyaccounts_trial_balance for balance-oriented questions. The agent must infer when this is the right call.

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