Reorder products

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

Annotations only indicate not read-only and not destructive, which is consistent. The description adds behavioral context by specifying that the entire list of product UUIDs must be provided, implying the tool replaces the full display order. This goes beyond schema and 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?

Two concise sentences, with the action stated first and the key usage detail second. No redundant or filler content.

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?

The tool has a single parameter and no output schema, so return values are not critical. The description covers the essential operational detail (full list requirement) and is fully adequate for the tool's simplicity.

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 coverage is 100% with a clear description of 'Product UUIDs in desired display order.' The description enriches this by adding the requirement that it must be ALL product UUIDs of the category, which is not stated in the schema properties.

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 uses a specific verb-resource pair ('Reorder products') and defines the scope ('within a category'). It clearly distinguishes from sibling tools like update_product or create_product by indicating a display-order operation.

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 sets clear context for when to use the tool (reordering products in a category) and provides a crucial usage instruction: pass ALL product UUIDs, not just a subset. However, it does not explicitly mention alternative tools or when not to use it, but no obvious alternative exists.

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