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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real context beyond that: the response is a non-paginated full list, and the endpoint (GET /taxes) is disclosed. It does not describe ordering or error behavior, keeping it at a 4.

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 with zero waste. The primary purpose is front-loaded, followed immediately by the operationally useful no-cursor note and endpoint.

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 input parameters and no output schema, the description carries the burden of return shape, and it does so by naming the fields returned. The structure of the 'rates' sub-object is not spelled out, a minor gap for a tool this simple.

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 and there are no parameter semantics to compensate for. The field list in the description pertains to output, not input, and is a bonus rather than a requirement here.

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 tax groups and their rates' – and enumerates the returned fields (id, name, is_default, rates), which clearly separates it from sibling list tools like list_brands or list_tags. Sibling differentiation is implicit rather than explicit, so it falls just short of a 5.

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 only one tax-related tool among the siblings, so usage is largely self-evident. The note 'the vendor returns the whole list in one reply (no cursor)' usefully tells the agent not to attempt pagination, but there is no explicit when-to-use vs.-alternative guidance.

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