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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses nullable semantics (image null means no public picture yet), vintage-neutral scoping (bottles carry the vintage), and a subtle constraint that only one correction may be pending per wine across all users plus whether it is the caller's own. That is meaningful behavioral context an agent could not infer from structured fields.

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 content is front-loaded, beginning with what the tool returns and ending with the trigger condition. It is dense and slightly over-packed into long compound clauses, but nearly every clause carries distinct, necessary 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?

There is no output schema, so the description carries the return-shape burden and does so by enumerating the record's fields and their null/absence behavior. Combined with the pending_correction and photo cross-references, an agent has everything needed to call and interpret this tool correctly.

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% and the single parameter is documented as 'Registry wine id from search_registry or a bottle's wine.' The description adds value by establishing that the id is vintage-neutral, clarifying that the same wine_id spans all vintages, which is not derivable from the schema.

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 opens with a specific verb+resource ('Full registry record for one wine') and enumerates exactly what the record contains, including the AI tasting profile and registry image. It is immediately distinguishable from siblings like search_registry, which it names as the predecessor step.

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 explicitly states when to call it ('after search_registry when the user wants depth on a specific wine'), routes to get_photo when the caller needs the actual picture, and instructs checking pending_correction before composing suggest_wine_correction. Both the trigger condition and adjacent alternatives are named.

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