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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real interpretive value by decoding the type codes (1 earning, 2 expenditure, etc.), which is exactly the kind of context annotations cannot carry. It says nothing about pagination, result ordering, or total counts, though the schema partly covers paging.

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?

It is a single compact sentence with no filler, but it is structured as a colon-delimited field glossary rather than being front-loaded with what the tool does. The reader learns the payload shape before learning the operation.

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, enumerating the returned fields is genuinely useful and partly compensates. However, a listing tool with zero required params still needs the action stated and some hint about scope or ordering; those gaps keep it at minimum-viable.

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% — limit and offset are both fully documented including the next_offset hint — so the schema does all the work. The description adds nothing about parameters, which is the expected baseline when coverage is complete.

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 enumerates the resource's fields ('account number, name, type, default tax, active/locked flags') which makes clear this is the chart-of-accounts resource, but it never states the action — no verb like 'list' or 'retrieve'. Sibling bexio_list_bank_accounts is not contrasted, so an agent must infer the difference between chart-of-accounts and bank accounts from the noun alone.

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 guidance on when to use this versus alternatives, no mention of the closely-named bexio_list_bank_accounts, and no note about filtering or scoping. The agent is left to infer that this is an unfiltered enumeration of the chart of accounts.

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