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

With no annotations provided, the description carries the full disclosure burden. It does add one genuinely useful behavioral detail: archived rates are excluded by default. However it says nothing about read-only safety, permissions, pagination, or what a returned rate contains — major gaps for a tool with zero annotation coverage.

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 no filler, and the archive-default caveat is front-loaded. The first sentence is a bare fragment that would be stronger leading with a verb, a minor structural weakness.

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 simple two-parameter read tool with no output schema, the description covers scope and the one non-obvious parameter entirely. It lacks any note on result shape or pagination, but for a plain rate listing that omission is minor.

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 coverage is 0%, so the description must compensate, and it does explain include_archived precisely: it governs whether replaced/removed rates appear, with default = excluded. shop_id is left uncharacterized, but its meaning (shop scope) is self-evident from the name and uuid format.

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 description names the resource ('the shop's tax rates') and the archived-exclusion note implies a listing, but it never states a verb and reads as a noun-phrase fragment. Nothing distinguishes it from siblings like taxes_saveRate, taxes_archiveRate, or taxes_salesReport, which an agent must infer from the name alone.

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 only implied: an agent must infer that this is the read-side tool for tax rates while taxes_saveRate/taxes_archiveRate mutate them. There is no explicit when-to-use, no prerequisite (e.g., required shop/account permissions), and no sibling routing.

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