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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds useful domain context — the returned fields, the fraction convention for rate (0.25 = 25 percent) — and notes the result is paged and comes from GET /taxRates, but says nothing about pagination termination, ordering, or rate limits.

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?

Extremely compact: resource and its fields first, then pagination, then the HTTP endpoint. No filler, though the telegraphic field list sacrifices some readability.

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 read-only, zero-required-parameter list tool with a fully documented schema, the description is largely sufficient, and it partly compensates for the absent output schema by naming the fields each record carries. It stops short of explaining what a filtered or empty result looks like.

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%, so both page and page_size are fully documented in the schema, including the cross-reference to next_page. The description's single word 'Paged' adds no syntax or defaults beyond that, so the baseline 3 applies.

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?

Names the resource (the company's VAT rates) and enumerates the fields the resource carries, plus the underlying endpoint GET /taxRates. The 'list' verb is implied by the tool name rather than stated in the description, and there is no explicit differentiation from sibling list tools such as billy_list_products or billy_list_accounts beyond the distinct resource name.

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?

'Paged' hints that pagination is involved but gives no guidance on when to reach for this tool versus a lookup elsewhere, and no prerequisites or exclusions. This mirrors the sibling list tools with no routing signal.

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