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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description still adds real behavioral context, notably that a search or lineup abv is a catalogue number, that null means unknown, and that get_claim must be used to inspect source evidence before asserting an alcohol requirement is met. It also states what the connection cannot do (orders, payments, catalogue-wide guarantees). Slightly repetitive phrasing dilutes it.

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?

Not front-loaded: the tool's actual function is buried mid-paragraph behind policy prose, and key instructions are restated ('Preserve declared wording' vs 'Preserve the source's exact alcohol wording'). Large blocks of refusal semantics crowd out the operational information an invoker 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?

Domain and refusal complexity are handled thoroughly, which matters given the open-world annotation and the absent output schema. But for a paginated list tool with 0% schema coverage, the description never explains pagination, defaults, or ordering, so an agent has no basis for advancing pages or bounding result sets.

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 0% across three parameters. The description only gestures at entity_type ('by type'), leaving the seven enum values and, more importantly, page and limit completely unexplained in prose and schema alike — no pagination or default behavior guidance despite this being a paginated list endpoint.

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 core purpose is stated precisely: 'List published entity profiles in the Beyond Wine knowledge base by type,' a clear verb+resource that reads differently from the get_entity/search_beverages siblings. The problem is placement — it sits after roughly five sentences of refusal policy, so an agent skimming the opening line sees catalogue scope, not a list tool. No explicit sibling contrast, but the list-vs-get-vs-search distinction is inferable.

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?

Unusually explicit about when-to-use and when-not: excluded categories (NA beer, NA spirits, mocktails, dealcoholized wine) should be declined without a lookup, purchasing requests declined without a lookup, and individual drink questions handled via claim wording and get_claim evidence. It names the alternative tool and the condition selecting it, which is exactly what this dimension asks for.

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