Free-text keyword search across HSN descriptions. Returns up to limit ranked matches (default 10, max 50). Use this when you have a product name but not a code.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max matches to return (1-50, default 10). | |
| query | Yes | Free-text query, e.g. 'basmati rice' or 'cement bricks'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosures. It explains the return behavior (ranked matches with configurable limit), and mentions default/max values. However, it does not state that the tool is read-only or describe potential side effects, which are minimal for a search tool. The disclosure is adequate but not exhaustive.
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 exceptionally concise with two front-loaded sentences: the first defines the action and behavior, the second provides usage guidance. No information is redundant or irrelevant.
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 tool's simplicity (2 parameters, no output schema), the description adequately covers purpose and parameter behavior. However, it omits the structure of returned matches (e.g., whether HSN code and description are included). A brief note on output format would improve completeness.
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 has 100% coverage, with descriptions for both `query` and `limit`. The description reinforces the `limit` behavior and clarifies the search scope ('across HSN descriptions'), but adds limited semantic value beyond the schema. It does not introduce new parameter meaning.
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 performs free-text keyword search across HSN descriptions, with specific details on result limits. It distinguishes itself from siblings by explicitly advising use when a product name (not code) is available, making purpose 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 provides a clear 'when to use' directive: 'Use this when you have a product name but not a code.' This implies the alternative (lookup_hsn) for codes, but does not explicitly exclude other contexts or list alternative tool names. It is useful but lacks full coverage of when-not-to-use.
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 has a distinct input and output: classify_product takes a product name and returns HSN codes; lookup_hsn takes an HSN code and returns description; search_hsn takes keywords and returns matching HSN descriptions. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern: classify_product, lookup_hsn, search_hsn. The verbs are distinct (classify, lookup, search) and the nouns correspond to the entity (product, hsn).
Three tools is appropriate for a specialized HSN classifier server. It covers the essential operations: classifying a product, looking up a code, and searching by keyword. Not too many or too few.
The tool set covers the main use cases (classify, lookup, search) but could benefit from a tool to list all HSN sections or chapters for hierarchical browsing. However, for the stated purpose of product classification, it is largely complete.