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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is fully covered. The description adds only that ids feed invoice lines; it says nothing about pagination, result volume, or default filtering behavior beyond what the is_archived schema field states.

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 action and scope, with the invoice-line context placed before the endpoint reference. The trailing 'GET /accounts' is mildly redundant but harmless.

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?

With no output schema, the description does not indicate what an account record contains (id, name, category) or whether results are paginated, which matters for a list tool with zero required parameters. It does supply the downstream-purpose context, which is the most valuable piece.

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 75%, so search, sort_dir and is_archived are already documented in the schema. The description adds a small amount by mentioning category-based listing (the one enum without a schema description) but gives no semantics for the values or how filters combine.

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 ledger accounts from the chart of accounts') and clarifies the scope with 'optionally by category'. The 'list' vs 'get' distinction from sibling bukku_get_account is implied by the name but never stated explicitly, so it falls short of full sibling differentiation.

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 note 'Account ids are used on invoice lines' implies the context in which an agent would call this (to obtain ids for invoice creation), which is genuine usage guidance. However, it never says when to prefer bukku_get_account for a single account, nor that filtering by category or archived state is the way to narrow results.

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