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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds substantive context by enumerating the fields returned and the 'live' real-time nature. It does not mention rate limits or output/error behavior, but that is a minor gap given the annotation coverage.

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?

Two sentences, zero waste. The field inventory is front-loaded and the parameter clarification follows compactly.

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 an output schema present, return values need not be explained, yet the description still previews the returned fields. For a one-parameter read tool this is nearly complete; only explicit sibling routing (e.g. when to use balenciaga_product instead) is missing.

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 carries the burden for the single url parameter. It usefully defines the accepted formats (product URL or a Product-Variation URL from balenciaga_product), which the schema 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?

States a specific resource with rich content detail ('live product variation matrix: colors, sizes, variation ids, sellability flags, care text, availability, and related product ids'). Clearly distinguishable from balenciaga_product by its variation-focused scope, though no explicit sibling contrast is made.

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?

Says the url 'may be a product URL or a Product-Variation URL returned by balenciaga_product', which routes the agent to the proper input source. However, it never states when to prefer this tool over balenciaga_product or what circumstances require it.

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