checkMultipleAllergens

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must convey behavioral traits. It states the tool 'checks' but does not explicitly confirm it is read-only, nor does it mention what happens on missing products, empty allergen lists, or error conditions. The behavior is implied but insufficiently detailed.

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, front-loaded sentence with no unnecessary words. It efficiently communicates the core function without redundancy.

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 tool has low complexity (2 required params, no output schema). The description covers the basic purpose but omits output details (e.g., boolean vs. list) and error handling. For a simple tool, it is minimally adequate but not complete.

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%, so the description adds little beyond the schema. It reinforces the 'multiple at once' aspect but does not clarify parameter format or constraints not already in the schema. Baseline of 3 is appropriate given full schema documentation.

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 function: 'Check if a product contains any of multiple allergens at once.' It uses a specific verb (check) and resource (product allergens) and explicitly distinguishes from single-allergen checks by mentioning 'multiple allergens at once', differentiating it from siblings like getAllergenCheck.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., getAllergenCheck for single allergen, getAdditivesInfo). The description lacks context on prerequisites, limitations, or exclusions, leaving the agent to infer usage independently.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.