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

Annotations already indicate a safe read-only operation, and the description adds meaningful behavior beyond that: media remains Shopify-hosted, no cart/checkout/order/payment is created, and the caller must prefer native image content while reproducing the Markdown fallback unchanged rather than converting it to HTML. These are operational traits an agent cannot infer from annotations.

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 dense but every clause earns its place: purpose, trigger, SKU guidance, fallback handling, a false-positive exclusion, a downstream routing instruction, and side-effect guarantees. The critical purpose and usage are front-loaded rather than buried.

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?

For a five-parameter tool with an output schema, the description covers purpose, routing, output handling, and side effects. The main gap is that it does not explain productHandle/category/limit/mediaTypes semantics in prose, though the schema enums and names are self-describing. An agent selecting the tool would have enough context not to misuse it.

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 of the five parameters only sku receives extra meaning ('Pass the exact live SKU to prioritize the image associated with its Shopify variant ID'). category, productHandle, limit, and mediaTypes are left entirely to their names and schema constraints.

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 opens with a specific verb+resource ('Read Shopify-hosted media data') and an explicit trigger ('when the buyer explicitly asks for additional images, videos, or a media gallery'). It also distinguishes itself from sibling display_homebridge_product_media by noting that the display tool should be called afterward only for an explicit media/gallery request.

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 an explicit when-to-use condition and a clear when-not-to-use: 'Do not call this after configure_homebridge_fire_pit merely to show the resolved product.' It also names the downstream alternative (display_homebridge_product_media) and the condition for switching to it.

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