Request that a product be added to the Low Tox Scanner index. Useful when scan_barcode returns product_found: false. Submission goes to a moderation queue.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | ||
| notes | No | Freeform context for the moderator | |
| barcode | Yes | 6–14 digit barcode | |
| category | No | ||
| product_name | No | ||
| ingredients_text | No | Comma-separated ingredient list copied from the product packaging |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that submissions go to a moderation queue (delayed action). Does not mention authentication, rate limits, or outcome clarity. Adequate but not comprehensive.
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?
Two sentences, front-loaded with purpose, then context. No wasted words. Efficient and clear.
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 moderate complexity, no output schema, and 6 params, the description covers the essential workflow (trigger after scan failure) and moderation queue. Lacks detail on response or constraints, but sufficient for most agents.
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 50%. The description adds no additional meaning beyond schema. Baseline 3 for medium coverage; no extra value from description.
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 specific verb 'Request that a product be added' and identifies the resource 'Low Tox Scanner index'. It also provides context linking to scan_barcode and distinguishes from sibling tools like scan_barcode.
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?
Explicitly tells when to use this tool: when scan_barcode returns product_found: false. Mentions submission goes to moderation queue, hinting at non-immediate outcome. Could be more explicit about when not to use or alternatives.
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 serves a distinct function: catalog stats, magnet guide samples, URL templates, barcode scanning, and missing product submission. No overlap in purpose.
All tool names follow a consistent verb_noun pattern with snake_case: get_catalog_stats, get_magnet_samples, get_resources, scan_barcode, submit_missing_product.
5 tools are well-scoped for a scanner/indexing service. Each tool provides necessary functionality without being overwhelming or too sparse.
Covers core operations: scanning, submitting missing products, retrieving catalog info, and resources. Minor gap: no tool to update product data or manage conditions, but these are handled via parameters or external links.