list_withholdings

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

No annotations, so description bears full load. Only states 'list' implying read-only, but omits details on permissions, pagination, returned fields, or any side-effect info.

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?

Single sentence, 7 words, all meaningful. Front-loaded with verb and resource. 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?

Adequate for a simple tool with one param and no output schema, but missing return format details (e.g., what fields are listed). Could add value without verbosity.

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 coverage is 100% with invoice_id adequately described. Description adds no extra meaning beyond 'for a specific invoice' already implied by name and schema.

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?

Description clearly states the action (list), resource (withholding tax deductions), and scope (specific invoice). Distinct from sibling tools as there is no other list_withholding tool.

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?

Clear context: use when you need deductions for an invoice. No explicit when-not or alternatives, but naturally implied since no other tool retrieves this data.

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