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

The description adds substantial behavior beyond the annotations: per-call pricing, free-tier rules, per-location error isolation without failing the whole call, confidence aggregation, agreement and freshness formulas, and data-source caveats. These are exactly the operational details an agent needs before invoking a paid batch lookup.

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 front-loads the batch purpose and pricing, and most sentences carry useful operational information. It is dense and semicolon-heavy rather than cleanly structured, especially around confidence and free-tier mechanics, but there is little pure filler.

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 paid batch tool with no output schema, the description explains ordering, per-location errors, aggregate confidence, and billing/free-tier behavior. It still relies on the sibling tax.sales_rate for the exact returned fields, but the invocation-relevant context is largely covered.

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 reported as 0%, so the description must carry parameter meaning. It partially clarifies that locations can be ZIP/ZIP+4/address matches and that bad dates fail per location, but it does not fully explain the required zip, optional date default/range, address field, or the 100-item limit in parameter terms.

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 precise batch behavior: the same answer as tax.sales_rate for each location, returned in order, with per-location errors. This clearly distinguishes it from the sibling single-location tax_sales_rate tool and the other tax/hospital siblings.

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?

It implies batch use for multiple locations and notes failure conditions such as locations outside SST states or bad dates. However, it does not explicitly say to use tax_sales_rate instead for a single location, so the alternative routing is only implicit.

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