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

Annotations only declare a safe read (readOnlyHint, openWorldHint, destructiveHint=false). The description goes well beyond them by disclosing capability boundaries: it cannot place orders or take payments, cannot guarantee zero alcohol, returns structured data plus claim previews, and requires following claim_uid into get_claim for evidence. That is substantive behavioral context an annotation cannot convey.

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 passage is grossly oversized for a fetch tool and front-loads scope policy rather than the operation. It repeats itself ('Preserve declared wording' / 'exact alcohol wording', multiple 'do not infer' variants), so many sentences are duplicative rather than additive.

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?

With no output schema the description does describe the return shape (structured data and claim previews), but a 3-parameter tool at 0% schema coverage still needs slug format and condensed semantics, which are absent. The extensive guardrail content is useful for domain conduct yet leaves the mechanical calling details thin.

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 0% and there are three parameters. The description lists four entity kinds (producers, beverages, people, restaurants) that map to part of the entity_type enum but omits ingredient, technique and prepared_ingredient, and says nothing about the slug format or what condensed changes. The description only partially compensates for the total coverage gap.

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 contains a clear verb+resource statement: 'Retrieve a published entity profile with structured data and claim previews,' and identifies what an entity can be (producers, beverages, people, restaurants). However, this core purpose is buried under a long policy preamble, and it never distinguishes this generic fetch from siblings like get_beverage or get_producer, leaving the agent to infer routing.

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 gives unusually explicit when-to-use and when-not-to-use guidance: refuse excluded categories, purchasing, and catalogue-wide guarantees without a lookup, and use get_claim for provenance. What it lacks is sibling-relative guidance — it never explains why an agent should call get_entity instead of get_beverage/get_producer for the same target.

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