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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's real contribution is behavioral: results are personalized by shelf proximity, tie-broken by popularity, and paged via nextCursor. That is useful disclosure beyond the structured fields. It does not say whether an empty or sparse shelf degrades the ordering, which is the one gap.

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?

Two sentences, zero filler, with the ranking semantics front-loaded before the pagination note. Every clause carries information an agent needs.

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 feed tool with no output schema, the description adequately conveys what the tool returns conceptually and how paging works. It leaves the shape of each recipe item unspecified, which an output schema would normally cover, so it is strong but not fully self-sufficient.

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 50%: cursor is documented in the schema, pageSize is not. The description's 'Paged with nextCursor' does corroborate the cursor parameter's meaning, but it adds nothing about pageSize (bounds 1-40, default 20) and no format details for the cursor itself. Baseline 3 is appropriate given the schema does half the work.

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?

It states a specific resource and its semantics: the Explore recipe feed, every drink, ordered by bottles-needed-from-your-shelf then popularity. That is distinguishable from siblings like explore_catalog or search_cocktails. It stops short of an explicit verb/contrast statement naming the sibling it differs from.

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 usage (browse the personalized Explore recipe feed) but never states when to pick this over search_cocktails or explore_catalog, nor any prerequisites such as having a populated shelf, which the ordering logic implies. Usage must be inferred from context signals, not the text.

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