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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses genuinely useful behavioral facts: no currency conversion is performed, the tool is free during validation, and no key/credits/wallet/preparation is required. These materially change how an agent plans around the call. It stops short of explaining failure modes or what happens on incompatible units.

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?

It is short and the core capability is front-loaded, but the back half degenerates into fragmented boilerplate ('FREE during validation.', 'Supply your task in input.', 'Existing source and input limits apply.') that reads as marketing/legal filler rather than useful specification.

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 tool with a complex nested input object, 0% schema coverage, and many overlapping siblings, the description is too thin. An output schema exists so return values need not be described, but the input contract and the distinction from commerce_pack_size_normalize/commerce_pack_plan are left unaddressed.

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 carry the burden, and it mostly does not. 'Supply your task in input' explains nothing about the nested currency/reference/offers structure, the decimal-string price format, or the unit enum. Only the '50 offers' cap and 'mass, volume or count units' loosely map to maxItems and the unit enum, which is partial compensation at best.

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: 'Compare up to 50 explicit pack prices with exact arithmetic across compatible mass, volume or count units', plus a scope limit ('no currency conversion'). It is clear on what the tool does, but it never distinguishes itself from close siblings such as commerce_pack_size_normalize, commerce_pack_plan, or agent_utilities_pack_preview.

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 when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. 'Existing source and input limits apply' is a vague catch-all rather than actionable routing advice, leaving the agent to guess between several price/pack-related tools.

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