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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only check but never states it explicitly, and it does not disclose whether the operation has side effects, requires special authorization, or how edge cases (unknown GTIN, unsupported banner) are handled. The core behavior is described accurately but thinly.

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 sentence with no filler that front-loads the core action. It is appropriately brief and every word earns its place.

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 covers return values, and the three flat, required parameters keep this manageable. However, with no annotations and no usage guidance, an agent must guess at prerequisites and edge-case behavior. For a simple check tool this is passable but not rich.

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%, so the schema documents nothing beyond parameter names. The description loosely maps to the parameters (GTIN, banner, country) but does not clarify what a 'banner' is (retailer chain), the format of country_iso, or expected value domains. With zero schema coverage, the description should compensate and does not.

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 states a specific verb-resource pair ('Check whether a GTIN can ship') with a precise scope (to a specific retailer banner in a country). This clearly distinguishes the action from resolve_gtin, find_makers, and find_retailers. However, it does not explicitly name or contrast the overlapping sibling tools.

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?

There is no guidance on when to use this tool versus its 13 siblings, such as resolve_gtin, get_signal_chain, or node_market. An agent has to infer that shipping-eligibility checks belong to this tool, but nothing states when it is the right choice, when it is not, or which alternative to prefer.

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