Retrieve current US sales and use tax rates for any address, ZIP code, city, or state - fully decomposed into state, county, city, and special district components plus the combined effective rate. Submit a full street address for the most accurate rate assignment. Premium API. Cost: $0.25 USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| lookup | Yes | Full street address, ZIP code, city, or state |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states 'Retrieve' implying a read-only operation, but the annotations indicate destructiveHint=true, creating a contradiction. The description does not disclose any behavioral traits beyond what annotations provide, and in fact contradicts them.
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 a concise three-sentence paragraph, front-loading the main purpose and including key details (decomposition, cost) without extraneous words. Every sentence earns its place.
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 single parameter and no output schema, the description fully covers the tool's functionality, including input types, output components, and cost. It is complete enough for an agent to use 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% for the single parameter. The description adds value by recommending a full street address for accuracy, which is not in the schema description. This enhances the agent's understanding of how to use the parameter effectively.
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 retrieves US sales and use tax rates for various inputs, distinguishing it from sibling tools which handle addresses, names, companies, etc. The verb 'retrieve' and specific resource 'sales and use tax rates' are explicit and unambiguous.
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 advises submitting a full street address for the most accurate rate assignment, providing useful guidance. However, it does not explicitly state when not to use this tool or mention alternatives, though the sibling list shows no other tax rate tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data operations (matching, standardization, enrichment) with clear descriptions. Minor overlaps exist, e.g., address_match_advanced vs global_address_match, but descriptions differentiate them.
All tools follow a consistent 'interzoid_descriptive_function' pattern in snake_case, making it easy to predict purpose from the name.
58 tools is high for a single server, exceeding the typical 3-15 range. While each serves a specific data enrichment function, the quantity may overwhelm agents without clear categorization.
The tool surface covers a broad domain including address, company, person, and financial data. Minor gaps exist (e.g., no reverse IP lookup, limited social media coverage), but core data needs are well-addressed.
