What should I pour tonight?

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds the suggestion dimensions (mood, occasion, season) but doesn't describe the exact return behavior, randomness, or personalization.

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?

A single streamlined sentence that leads with the core proposition and then lists the relevant factors. There is no filler or repetition.

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?

For a simple system with three optional parameters and no nested schemas, the description is adequate and complete enough for a basic agent. The main gap is not mentioning what the suggestion looks like or how it differs from the sibling suggestion tool.

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?

The description enriches the schema by providing concrete examples for mood ('unwinding', 'celebratory') and occasion ('nightcap', 'with friends'), which helps specify valid literal values beyond the generic parameter descriptions.

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 tool's function: a pour suggestion for right now based on mood, occasion, and season. It is purposeful but does not distinguish itself from siblings like get_recommendations or trending_bottles.

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?

The description implies when to use this tool via 'for right now' and gives reasons like mood, occasion, and season, but it does not mention alternatives or explicitly state when not to use it.

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