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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHnt=false, covering the safety profile. The description adds the behavioral notion that results are personalized based on the listed inputs, which is useful context beyond schema, but it does not disclose response format, ordering, or no-match behavior. No contradiction with annotations.

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 that immediately conveys the core purpose and lists the relevant inputs without fluff. The inline examples are mild but not wasteful; it could be marginally tighter, but it is concise and readable.

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 read-only tool with fully documented parameters, the core invocation details are present. However, with no output schema, the description does not clarify what the returned 'picks' contain, how they are ordered, or what happens when no coffee matches. This is enough to call the tool but not fully self-contained for an agent.

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% and every parameter already has type, constraints, and examples. The description merely paraphrases the inputs (flavor preferences, budget, roast, brew gear) without adding semantic detail such as how budget interacts with recommendations or how limit applies, so it does not raise the 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?

The description states a specific action (get) and resource (coffee recommendations) and characterizes them as personalized picks driven by taste, budget, roast, and brewing equipment. This differentiates it from siblings like trending_coffees or search_coffees, though it does not explicitly name alternatives, so it stops short of a 5.

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 when-to-use guidance or exclusion criteria is provided. The description implies a personalization use case, but the agent is left to infer when get_recommendations is prefered over search_coffees, find_similar, or trendig_coffees. Explicit routing would be needed for a 4 or 5.

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