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

readOnlyHint=true already tells the agent this is a safe read. With no output schema, the description usefully discloses the shape of the returned records (tax name, rate or fixed amount, inclusive/exclusive, claimable, reference number), which is real added value. However it says nothing about pagination, ordering, or auth scope, so it is solid but not rich.

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 sentence with the resource front-loaded and the returned fields enumerated compactly. No wasted words, though the trailing field list is a touch dense.

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 no-parameter, read-only list tool with no output schema, the description covers both what the tool does and what comes back, so an agent has enough to invoke it correctly. Minor gap: no mention of ordering, pagination, or result size.

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 correctly implies no filtering or input is needed, and there are no parameters to mis-specify.

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 (List) and resource (the business's sales taxes), and enumerates the exact attributes returned (name, rate/fixed amount, inclusive/exclusive, claimable, reference number). This clearly distinguishes it from sibling mutations like add_entity_salestax, update_entity_salestax, and the related get_sales_tax_classifications.

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?

Usage is implied by the name and the read-only nature of the tool, but there is no explicit guidance on when to call it versus alternatives such as get_sales_tax_classifications, nor any preconditions or exclusions. Adequate minimum-viable context, but nothing that routes the agent among siblings.

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