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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by explicitly ruling out side effects ('does not write a bottle or set expressionRef,' 'never generates art') and by describing the response shape with a confidence score, which is behavioral context the annotations do not provide.

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 purpose is front-loaded in the first clause and every sentence carries information (input modes, return fields, exclusions). It is a single dense paragraph with some parenthetical internal function names that could be trimmed, but there is little outright waste.

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?

With no output schema, the description would need to carry the return-value burden, and it does enumerate the expected returns (distillery, location, spirit.brand + expressions incl. name/proof/msrp/tasting_notes, success, confidence). Combined with annotations that cover the read-only profile, the definition is complete enough to call correctly, though it omits what happens when confidence is low or neither input resolves.

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 100%, so both parameters (query, imageData) are already documented in the schema and the baseline is 3. The description reinforces that they are alternatives ('Photo (imageData) or text (query)') but adds no format, precedence, or fallback detail beyond what the schema states, so it does not rise above baseline.

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 a specific verb+resource ('AI identify' a bottle from photo or text) and explicitly differentiates from the write path by saying it 'does not write a bottle or set expressionRef,' which separates it from add_bottle. It's clear, though the phrasing leans on internal function names ('Add-bottle AI identify (analyzeBourbonImage)') that read as jargon rather than a clean purpose statement.

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?

It implies usage by noting either photo (imageData) or text (query) can be supplied and by clarifying that it is not a write operation, which nudges the agent away from add_bottle. However it never names reidentify_bottle, get_expression, or any sibling as the alternative, nor states when this lookup is preferred over reidentification. Usage is inferred rather than guided.

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