get_ingredient_info

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

No annotations provided, so description must carry burden. It discloses what information is returned (description, type, alcohol content) but does not mention side effects, prerequisites, or any state changes. As a read-only lookup, it's adequate.

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?

Single sentence, no wasted words. Front-loaded with main action 'Get detailed information'.

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 simple input schema, no output schema, and no annotations, the description is complete enough for a basic lookup. Could mention the return format or that it may return null if not found, but not essential.

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% with a single parameter 'ingredient' described as 'Ingredient name to look up'. Description does not add much beyond schema, but parameter is straightforward. Baseline 3.

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?

Description clearly states the tool retrieves detailed information about a cocktail ingredient, specifying attributes: description, type, and alcohol content. It distinguishes from siblings like 'search_by_ingredient' which likely searches for cocktails by ingredient, not info about the ingredient itself.

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 explicit when-to-use or when-not-to-use guidance. The purpose is clear but does not mention alternatives or exclusions. Implicitly, this tool is for ingredient details rather than cocktail lists.

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