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

readOnlyHint=true is consistent with "List"; the description adds the underlying API call (GET /tax_codes) and the exact return fields, which annotations don't convey. It does not state whether the catalog is paginated or cached, so it is good but not fully transparent.

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?

A single front-loaded sentence delivers purpose, return fields, and downstream use, followed by a one-line API reference. Nothing is padded or redundant.

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 carries the burden of describing returns and does so by naming the three fields. It omits any mention of result ordering or whether the list is static, a minor gap for a trivial zero-param read.

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 the baseline is 4. The description helpfully documents the response shape (id, name, description) in place of any parameter discussion, adding value rather than repeating schema content.

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 the product tax codes Quaderno supports") and even enumerates the returned fields (id, name, description), so the agent knows exactly what comes back. No sibling lists tax codes, so differentiation is implicit but unambiguous.

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 clause "used as the tax_code on products / tax calculations" tells the agent when this tool is relevant — before creating items or running tax calculations. It stops short of explicitly naming a prerequisite sequence or alternative, but the use context is clear.

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