tax_rate

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

With no annotations provided, the description carries full burden. It discloses date-sensitivity, handling of historical/temporary changes, US returning 0 for national VAT, and dependence on state code. However, it does not specify the return format (e.g., decimal or percentage) or error behavior, leaving minor gaps.

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 concise, with every sentence adding value. It is front-loaded with the critical instruction to use this tool before tax calculations, followed by clear behavior and parameter guidance. No superfluous words.

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?

Given no output schema, the description covers the tool's purpose, parameters, and usage well. It lacks explicit detail on return values or error handling, but for a tax rate tool the provided information is largely sufficient for correct invocation.

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%, so baseline is 3. The description adds value by reinforcing parameter usage: it emphasizes passing the invoice date for GB and clarifies that state is for US sales tax. This contextual guidance improves semantics beyond the schema alone.

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 the tool returns tax rates (VAT or sales tax) for GB or US, with date sensitivity and state-specific handling. It distinguishes itself from sibling tools (none are tax-related) and uses specific verbs and resources.

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 explicitly instructs to use this tool before calculating tax, warns against recalling rates from memory, and provides specific guidance for GB (always pass invoice date) and US (pass state code for sales tax). It clarifies when to use each parameter and implies no alternatives among siblings.

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