Available product search criteria (materials, sectors, certifications, Atex zones, power, capacity, etc.). Call before configureProduct.
| Name | Required | Description | Default |
|---|---|---|---|
| search | No | Optional text filter to narrow returned options | |
| includeEmpty | No | If true, include terms with no published products |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explicitly state that the tool is read-only, what the output structure looks like, or any side effects. The phrase 'Available product search criteria' implies a list is returned, but the lack of return format and safety information leaves a significant transparency gap.
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 single sentence that front-loads the main purpose and includes a clear usage instruction. It is concise, with no redundant information, and every clause serves a distinct function.
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 the tool's purpose and usage directive, which is acceptable for a simple tool with optional parameters. However, without an output schema or annotations, it does not describe the response structure or safety profile. The description is adequate but leaves some contextual gaps that the agent must infer.
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% description coverage for both parameters, so the baseline is 3. The description adds some context by listing the categories (materials, sectors, etc.) that the 'search' parameter filters over, but it does not add specific parameter semantics beyond the schema and does not mention 'includeEmpty' at all.
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 provides available product search criteria, listing examples like materials, sectors, and certifications. It also explicitly directs the agent to call it before configureProduct, distinguishing it from sibling tools that fetch individual data categories.
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 gives a clear usage directive: 'Call before configureProduct.' This provides a strong temporal context for when to use the tool. However, it does not mention alternatives or exclusions, but the sequential guidance is sufficient for basic usage.
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 reference attributes (e.g., applications, sectors, capacities). A few overlaps like motor/power/total power and Atex categories/zones could cause misselection, but descriptions clarify.
All tools use get + Noun camelCase; configureProduct is the sole exception, which slightly breaks the pattern but is semantically clear.
20 tools exceed the typical well-scoped range, making the server feel heavy, though each tool has a specific role in the industrial vacuum configurator.
Covers search criteria, detailed specs, accessories, and product configuration. Missing a general product listing or comparison tool, but core workflows are supported.
