teamleader_tax_rates_list

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, 'List tax rates' only states the basic operation and does not reveal pagination behavior, response format, or any side effects. The agent gains no additional insight beyond the tool name.

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, short sentence, which is concise and front-loaded. However, it is under-specified rather than efficiently informative, so it does not fully earn its place as a complete tool description.

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 and no annotations, the description should explain return values and behavior. It does not mention what the list returns, whether pagination is implicit, or any other context. The tool is a simple list, but even basic details are missing, making the description inadequate for an agent to invoke it confidently.

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?

The schema has two parameters with 50% description coverage (page has no description, page_size has 'max 100'). The tool description adds no parameter information, so it does not compensate for the gap. The parameter names are somewhat self-explanatory, but the description fails to clarify their usage or formatting.

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 'List tax rates' clearly states the action and resource, but it essentially restates the tool name (teamleader_tax_rates_list) without providing differentiation from the sibling tool teamleader_withholding_tax_rates_list. It is more informative than a pure tautology but lacks scope or distinguishing details.

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 offers no guidance on when to use this tool versus alternatives, such as teamleader_withholding_tax_rates_list. There is no mention of context, prerequisites, or exclusions, leaving the agent without any usage direction.

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