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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful provenance by saying the data comes from Nike's anonymous mobile backend and lists shipping levels such as HIGH/LOW/MEDIUM/OOS. However, it does not describe auth requirements, rate limits, or other behavioral constraints beyond what the annotations and output schema already provide.

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 front-loaded sentence that efficiently states the purpose and then lists data fields. It avoids wasted preamble, though the output-field list is somewhat redundant with the output schema. It remains appropriately sized for the tool.

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?

Because an output schema exists, the description need not detail return values, and annotations cover read-only behavior. However, the required group_key parameter is completely undocumented in both the schema and the description, leaving an agent without enough information to invoke the tool correctly. The provenance and output hints help, but the input gap is significant.

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?

The schema has one required parameter, group_key, with 0% description coverage. The description never mentions group_key or explains what value to supply, where to obtain it, or how it identifies a product. With a required undocumented parameter, the description fails to compensate for the schema 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 states a specific verb and resource: per-size shipping availability for one Nike product. It clearly distinguishes availability from sibling tools like nike_product_details and nike_product_reviews, though it does not explicitly name those alternatives. The output fields are also enumerated, reinforcing the tool's purpose.

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 alternatives such as nike_product or nike_product_details. It does not state prerequisites or how to obtain the required group_key input. The only implied usage is that an agent needs per-size shipping availability for a known Nike product.

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