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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds that product URLs are read live at load and POS counts are included only if the banner record carries a cited one, which is useful context. However, it doesn't clarify authentication or rate limits beyond the decision_id requirement.

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 description is a single sentence but it's overly long and parenthetical-heavy, which hurts readability. Information is front-loaded with 'In stock, and where', but the rest is cluttered with jargon.

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?

Given that an output schema exists, the description needn't explain return values. However, it should still clarify parameters and behavioral aspects. The gate_transaction dependency is covered, but parameter semantics are lacking, and the overall domain context is opaque.

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 but doesn't. It implies a gtin and decision_id are needed, but doesn't explain market parameter, its format, or its impact. No meaning is added beyond what's in the schema names.

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 attempts to convey the purpose but the phrasing is convoluted and non-standard. It includes domain-specific terms (banners on the shelf of record, product URLs read live at load) that are jargon-heavy and don't clearly distinguish it from siblings like get_price or get_item. A reader can infer it returns availability data, but the delivery is muddled.

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?

The description explicitly states the prerequisite: 'once gate_transaction has answered allow (decision_id)'. This clearly tells the agent when to use the tool (after gate_transaction) and what's needed. However, it doesn't specify alternative tools or when not to use it.

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