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

Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds no behavioral detail beyond that: no mention of pagination, ordering, or what the mapping entries contain. Since there is no output schema, this gap is more costly than it would otherwise be.

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, zero filler, and the resource definition is front-loaded ahead of the sibling routing. Nothing in the text is redundant with the name or title.

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 zero-param list tool the description covers purpose and routing, but with no output schema an agent still cannot anticipate the shape of the returned mapping entries. It is minimally adequate rather than complete.

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?

The tool takes zero parameters, so there are no parameter semantics to describe; baseline 4 applies. The description correctly spends its words on resource identity instead of inventing parameter guidance.

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 noun phrase 'chart-of-accounts category-to-account mapping' names a specific resource, and the name supplies the list verb, so the intent is unambiguous. It also explicitly distinguishes itself from the closest sibling (list_accounts), though it never states outright what it returns.

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?

'For the accounts themselves use list_accounts' is an explicit alternative with the condition that selects it, which is exactly the routing guidance an agent needs. It gives no other usage conditions, but with zero parameters there is little else to condition on.

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