Semantically match a plain-English company description to 2022 NAICS industry codes. Returns ranked codes with a 0-100 match rating, hierarchy, and the official Census activities that matched. Keyless trial of the NAICS Code Finder API.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Company description, capabilities, or services (3-1000 chars). | |
| limit | No | Number of matches (default 5). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the return format (ranked codes, 0-100 rating, hierarchy, activities) and indicates it's a keyless trial. However, it does not specify behavioral traits such as rate limits, authentication needs, or whether the operation is read-only. The description is adequate but incomplete.
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 two sentences, front-loaded with the main purpose, and contains no superfluous information. Every sentence adds value: the first states the core functionality, the second adds trial context.
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?
The description explains what the tool returns (ranked codes, rating, hierarchy, activities) and covers the input parameters clearly. Since output schema is absent, the description compensates well. Missing information about authentication or usage limits is minor given the 'Keyless trial' indication.
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 100%, so the schema already documents both parameters. The description adds the context of 'Keyless trial' but does not provide additional semantics beyond what is in the schema. Baseline 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 clearly states the action (semantically match), the input (plain-English company description), the target (2022 NAICS industry codes), and the output (ranked codes with rating, hierarchy, activities). It is specific and distinguishes from sibling tools which perform different operations like fetching URLs, converting currency, etc.
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 implies the tool is for matching company descriptions to NAICS codes, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. The mention 'Keyless trial' hints at possible usage limits but lacks clear instructions.
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.
Each tool targets a distinct functionality (fetching URLs, converting currency, validating email, geolocating IPs, listing APIs, matching NAICS codes, fetching URL metadata), with no overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., currency_convert, ip_lookup, naics_match, ensuring predictability.
Seven tools is well-scoped for an API catalog service providing trial endpoints for a variety of utilities—neither too sparse nor overloaded.
The set covers key read-only operations for each featured API, though missing write or list operations (e.g., listing supported currencies) are minor gaps that users can work around.
