list_taxtables

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

No annotations are provided, so the description carries full disclosure burden. It reveals substantial behavioral detail: the leading 'Showing X-Y of Z taxtables' line, pagination semantics, limit=0 count-only special case, compact vs verbose output differences, and resolved account paths/refcount in verbose mode. This is rich behavioral context beyond mere intent.

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 well-structured with clear sections and front-loaded purpose. It opens with the purpose, explains output formats with a memorable example of the leading line, then concisely documents each parameter in a compact Args block. Every sentence adds value with zero filler.

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?

This is a moderately complex list tool with format toggling, pagination modes, and count-only special case, but has an output schema present. The description is thorough for selecting and invoking correctly. It slightly misses explicit detail on the exact shape of the compact per-line output (what fields constitute 'rate→account routing'), but overall a list tool with this richness is nearly complete.

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 0%, so the description must fully compensate. It does: verbose ('return full JSON for each taxtable'), limit ('page size default 50 max 250, 0=count only'), and offset ('0-indexed first row'). All three parameters get meaningful semantic detail beyond the bare schema definitions.

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 all sales-tax tables' with a specific verb and resource. It distinguishes pagination behaviors, compact vs verbose formats, and the count-only mode, which sets it apart from sibling taxtable tools (get/update/delete/create).

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 explains when to use this tool for listing taxtables, and documents key usage behaviors like pagination (offset/limit), count-only mode (limit=0), and output format selection (verbose). It doesn't explicitly name non-list siblings as alternatives, but the list context is clear and it covers the main usage decisions.

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