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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully carried by structured data. The description adds only that the categories are the ones used for categorizing transactions, with no mention of scope, pagination, or completeness of the returned list.

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, front-loaded with purpose and followed by trigger conditions; no filler. The parenthetical '(chart of accounts)' slightly restates the title but earns its place as the common user term.

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 only two optional parameters, complete schema coverage, no output schema, and rich read-only annotations, an agent has everything needed to call it. The only real gap is the missing differentiation from list_categories.

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% - both the type enum values and the company/default resolution rule are fully documented in the schema. The description adds nothing about either parameter, so baseline 3 is 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 account categories (chart of accounts)') and clarifies these are categories used to group transactions. It stops short of distinguishing this from the sibling list_categories, which reads as the nearest overlap, so the agent cannot fully rule out the wrong tool from the description 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?

The second sentence gives concrete triggers - the user asking about their chart of accounts, account codes, or available categorizing categories. There are no exclusions or named alternatives, even though a sibling list_categories exists, so a common ambiguity is left to inference.

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