List taxes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the specific content detail (included/added to price), but doesn't mention any other behavioral aspects like rate limits or pagination. It provides minor value beyond the annotations.

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, clear sentence with zero filler. It is appropriately front-loaded with the core purpose and the key distinguishing detail. Perfect conciseness.

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 list tool with no output schema and 6 optional filter parameters, the description is minimal. It doesn't explain that parameters are filters, or describe the return format. While annotations cover safety, the description leaves some operational details ambiguous, though the schema partially fills the gap.

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 67% (4 of 6 parameters have descriptions), so the description should compensate for the undocumented tax_ids and show_deleted parameters. However, it provides no parameter guidance whatsoever, leaving those two parameters entirely unexplained.

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 uses a specific verb ('List') and resource ('tax rates'), and adds the distinctive detail of whether each tax is included in or added to the price. This clearly distinguishes it from sibling tools like loyverse_upsert_tax and other list operations.

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 description makes the tool's purpose obvious for listing tax information. While it doesn't explicitly mention alternatives or exclusions, the context of the sibling tools (upsert_tax vs list_taxes) makes the usage clear without needing explicit routing.

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