List taxes

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

No annotations provided, so the description carries full burden. It discloses pagination support (cursor, fetch_all), adherence to API v1.0 docs, and error behavior (400 returns verbatim message). It does not explicitly state it is read-only, but the 'GET' method and 'list' imply no modification. Additional details like authentication or rate limits are missing.

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?

Three sentences deliver the essential purpose, pagination support, and error behavior. Each sentence adds value without redundancy. Front-loaded with the main action.

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?

No output schema, so the description should explain return format. It mentions listing taxes and pagination but does not specify that the response is a list of tax objects. Given the complexity (4 params, nested objects) and lack of output schema, the description could be more explicit about what the tool returns.

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 100% with clear descriptions for all 4 parameters. The description adds context about pagination ('Supports cursor pagination') and error handling ('adjust fields'), but these are partially implied by the schema. No new parameter meaning beyond what the schema provides.

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 clearly states 'List taxes' and provides the API endpoint (GET /taxes). It is specific about the resource (taxes) and action (list), and the name and title match. Among many list siblings, it distinguishes itself by explicitly naming the resource and endpoint.

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 implies usage by stating 'List taxes', which is clear for listing vs. getting a single tax (use get_tax instead). No explicit alternatives or when-not-to-use, but the context is clear enough. The error handling tip ('adjust fields and retry') provides some guidance but not about tool selection.

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