list_tax_descriptors

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

No annotations are provided, so the description bears the full burden. It conveys that the tool is a read-only list operation (via 'List'), but does not explicitly confirm safety, specify authentication needs, or describe pagination behavior. The inclusion of code examples adds some value, but the lack of explicit behavioral details limits transparency.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's purpose and key details (the specific codes). Every part earns its place with no redundancy.

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 list tool with an output schema and self-documenting parameters, the description adequately covers the resource and its identifiable codes. However, it does not clarify that the listed codes are examples or exhaustive, nor does it mention that results are paginated. Overall, it is complete enough for agent invocation but has minor gaps.

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 100%, so the schema already documents all four parameters (sort, fields, page_size, page_number). The description does not add any parameter-specific meaning beyond the resource identification, so it meets the baseline but does not exceed it.

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 explicitly states it lists tax descriptors, identifies them as VAT rates, and enumerates the specific codes (NOR, INT, RED, ISE). This clearly distinguishes it from sibling list tools like list_customers or list_products.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusion criteria, or compare to similar list tools, leaving the agent to infer usage from context.

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