accelo_list_taxes

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

No annotations are provided, so the description carries full burden; 'List' implies a read-only operation but this is never stated. It does disclose pagination behavior (page is 0-indexed, limit maxes at 100), which is useful beyond the schema, but says nothing about permissions or result ordering beyond the order_by filter keys.

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?

Front-loaded with purpose, then a compact domain note and an Args block. Every line is short and useful, with only minor slack in restating that tax codes define tax rates applied to invoices/expenses/materials.

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?

With no output schema, the description partially compensates by naming the key returned fields (title, rate, standing) and by documenting pagination and filtering. Missing only read-only/safety context, which annotations would normally have supplied.

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% and all four parameters are documented in the description: filters keys (id, standing, order_by_asc/desc), fields with a concrete example ('rate,standing'), page 0-indexed, and limit max 100. This meaningfully compensates for the empty schema descriptions, though filter value formats are still unspecified.

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?

States a specific verb+resource ('List tax codes from Accelo') and adds a one-line explanation of what a tax code is and which records it affects. It is distinguishable from accelo_get_tax and accelo_count_taxes by the 'list' verb, though it never explicitly names those siblings to route the agent.

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?

Gives no when-to-use or when-not-to-use guidance relative to accelo_get_tax, accelo_count_taxes, or the adjacent accelo_list_rates / accelo_get_rate tools. The agent must infer that this is the enumeration endpoint and rates are a separate resource.

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