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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds a prerequisite (decision_id required) and the result shape (URL plus read date and source class), but since an output schema exists those return details are largely redundant and no auth/rate-limit/permission context is added.

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?

A single dense sentence that front-loads the resource and its contents ahead of the required-parameter note. Every clause carries information, though the parenthesis of document types is long enough to slightly dilute the sentence.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a 3-parameter tool with 0% schema description coverage, leaving market unexplained and not naming gtin explicitly means the definition is only marginally complete.

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, so the description must carry the burden. It notes that decision_id is required (already visible in the schema's required list) and vaguely implies gtin via 'on an item record', but the market parameter is never mentioned or explained, leaving a real 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 names a specific resource (documents on an item record) and enumerates the document classes it returns (organic certificate, PDO/PGI, halal, kosher, specification, allergen statement), which is far more informative than the bare title. It does not explicitly contrast itself with the close sibling get_label_and_claims, so an agent must infer the boundary.

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?

Usage is only implied: the 'each a URL with its read date and source class' phrasing tells the agent what to expect, and 'decision_id required' signals a prerequisite. There is no statement of when to call this versus get_label_and_claims, get_item, or get_market_status, and no exclusions.

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