calculate_tax

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

No annotations are provided, so the description carries full burden. It mentions returning 'audit trail and advisories' which hints at behavior, but doesn't say whether it's read-only, whether it mutates anything, what permissions are needed, or whether the calculation is deterministic. For a 9-param tax calculation tool this is a significant gap.

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?

Two efficient sentences with no filler; the purpose is front-loaded and the return contents are summarized compactly.

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 annotations, no output schema, and 9 parameters, the description is minimally adequate but leaves real gaps: it doesn't explain when to prefer siblings, what the 'advisories' mean, or how the audit trail is structured. Given the complexity of multi-jurisdiction tax calculation, more context would help an agent call it correctly.

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 the schema already documents all nine parameters including enums and constraints. The description adds no parameter-level detail (e.g., that role affects the calculation direction, or that work_type drives per-state classification in tandem with transaction_type). Baseline 3 is appropriate given the schema does the heavy lifting.

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 states a specific verb (calculate) and resource (US sales tax / use tax) with a stated scope tied to AI agent transactions. It doesn't differentiate itself from siblings like get_rates or track_payment, but the purpose is clear and accurate.

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 says what it does but never says when to use it versus get_rates, track_payment, or configure_nexus. There's no mention of prerequisites (e.g., need buyer_state and buyer_zip for accuracy, or that this is the right tool before a transaction completes).

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