teamleader_withholding_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. It simply states 'List withholding tax rates' without indicating pagination, result format, read-only nature, or any side effects. While listing implies a read operation, the description does not explicitly confirm safety or explain behavior beyond the action itself.

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 extremely concise with no wasted words, and the key action and resource are front-loaded. However, it might be too terse, lacking structural elements like additional clauses that could clarify scope or behavior, but it is appropriately sized for the minimal content it presents.

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?

The tool is a simple list operation with two optional params, but the description omits critical context: no mention of pagination, no output schema, no annotations, and no differentiation from the similar sibling 'teamleader_tax_rates_list'. For an agent to decide correctly, more contextual detail is needed, especially about the distinction between withholding and regular tax rates.

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 50% (only page_size has a 'max 100' description, page has none). The description adds no parameter semantics, leaving 'page' completely undocumented and not clarifying the meaning of 'page_size' beyond the schema. It fails to compensate for the incomplete schema coverage.

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 withholding tax rates.' clearly states the action (list) and the specific resource (withholding tax rates), distinguishing it from the sibling tool 'teamleader_tax_rates_list' which covers regular tax rates. The verb+resource pairing is unambiguous.

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. There is no mention of the difference between withholding tax rates and regular tax rates, nor any context about when this list is relevant. No exclusions or alternative recommendations are given.

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