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

Annotations already declare readOnly/openWorld/non-destructive, and the description goes well beyond them: it discloses that the connection cannot place orders or take payments, cannot guarantee zero alcohol, and that pagination (meta.has_more) must be followed before making negative findings. It also warns against inferring absence from wording differences and against inventing products or producers.

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 content is valuable but sprawling and repetitive, reading more like a policy prompt than a tool definition. The central purpose sentence appears well after the exclusion catalogue, so the description is not front-loaded. Several refusal-related sentences could be condensed or moved to system-level guidance.

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 correctly names the return structure pieces an agent needs (provenance.sources, meta.has_more) and explains how to interpret declared alcohol wording. It is fairly complete for a search tool, though page/limit behavior and the exact response shape remain unaddressed.

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%, so the description must compensate, and it largely does: it explains that claim_type is a record format (atomic_fact, structured_fact, editorial_claim) NOT a topic, that entity_type must be paired with an exact entity_slug, and that claim_type/reliability_class are optional refinements. It says nothing about page or limit, leaving two of six parameters unexplained.

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 mid-description: 'Find published claims with their source provenance,' giving a clear verb and resource. However, the description opens with a lengthy domain-scope essay about what Beyond Wine excludes, so the actual function of the tool is buried rather than front-loaded. It differentiates itself from siblings by describing the claim-record domain and provenance focus, but does not explicitly name a sibling alternative.

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?

Explicitly states when to use it (individual drink/producer questions, sourced statements), how to invoke it (supply BOTH entity_type and the exact entity_slug), and when to omit filters (omit claim_type and reliability_class unless needed). It also gives precise when-not guidance: explain scope or decline purchasing/guarantee requests WITHOUT a lookup, since an empty search does not establish exclusion.

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