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

No annotations are present, so the description carries full burden. It only states a high-level outcome and gives no details on what inputs are used, what thresholds apply, or what the tool returns (e.g., a list of states, a boolean, or a threshold comparison).

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 short, but that brevity comes at the cost of usefulness. It doesn't provide actionable guidance, making it under-specification rather than efficient conciseness.

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 the complexity of US economic nexus rules and the lack of an output schema or annotations, the description is inadequate. It doesn't mention the threshold logic, the role of transactions count, or how results are presented.

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?

The input schema describes all three parameters (sales, state, transactions) with clear semantics and ranges. The description adds no additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the resource ('US sales tax') and implies an outcome ('where you must collect'), but uses the vague verb 'see' instead of a specific action like 'determine' or 'check'. It doesn't distinguish from siblings like us-sales-tax-calculator, which also relates to US 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 guidance on when to use this tool versus alternatives. It doesn't mention that this checks economic nexus thresholds vs calculating tax amounts, nor does it clarify prerequisites like annual sales/transactions data.

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