sales_tax_calculator

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions inputs and a default tax rate, but does not state the output format (e.g., total price after tax), rounding behavior, or any side effects. The behavior is implied but not explicit.

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 the core purpose front-loaded in the first clause. Every word adds value, and it includes the key input details in a compact manner.

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?

For a simple calculator, the description covers the purpose and inputs, but omits explicit output details (e.g., whether it returns total or tax amount) and any edge-case behavior. Given no output schema, this gap could cause ambiguity for an agent.

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 0%, so the description must add meaning. It explains that taxRate is a percentage (%) and provides a default of 8, which goes beyond the bare schema. However, it does not clarify price's unit or format, and the description is minimal.

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 verb ('Add') and the resource ('sales tax to a price'), making the tool's purpose unambiguous. It also implicitly differentiates from sibling calculators (discount, fees, margins) by naming a specific domain (sales tax).

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?

No explicit guidance is given about when to use this tool versus the many sibling calculators. The description does not mention alternatives or conditions, leaving the agent to infer usage solely from the name and brief statement.

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