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

readOnlyHint=true already declares the safety profile, so the description needn't restate that it is a read. It adds the concrete endpoint (GET /finance/accounts), which is useful confirmatory context, but says nothing about pagination defaults, result ordering, or cost of requesting balances.

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?

Two short sentences with the core capability front-loaded and zero filler; the API endpoint is a compact, useful addendum rather than padding.

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 simple read-only, fully schema-documented list tool with annotations covering safety, this is nearly complete. The only residual gap is that, with no output schema, the description does not sketch what an account record or balance value looks like.

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%, so all four parameters (page, search, per_page, include_balance) are already documented in the schema. The description's "optionally with balances" reinforces include_balance but adds no syntax or behavioral detail beyond the schema, making baseline 3 appropriate.

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 accounts of the chart of accounts") plus an optional capability (balances), which is enough to distinguish it from report tools like kledo_report_trial_balance. It does not, however, explicitly contrast itself with kledo_get_bank_balances or the report siblings, so an agent must infer the boundary.

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?

There is no explicit when-to-use or when-not guidance and no named alternative. The phrase "optionally with balances" hints at the include_balance parameter but does not tell an agent when to prefer this list over kledo_get_bank_balances or a balance-related report.

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