cache_purge_product

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

No annotations are provided, so the description carries the full burden. It only states 'Purge cache' without any details on side effects, scope, idempotency, or confirmation of success. For a destructive action, more behavioral context is needed.

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 very short (one sentence), which is concise but under-specified. It lacks critical details about parameters and behavior, making it less useful despite its brevity.

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?

Given the complexity (sibling cache purge tools, no output schema, vague parameter), the description is insufficient. Missing information about required inputs (SKU), return values, and prerequisites for usage.

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 input schema has one parameter 'params' described as 'Action parameters as a JSON object', which is vague. The description mentions SKU but does not specify its location or format within the params object. The schema coverage is high but the description adds minimal meaning.

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 clearly states the action ('Purge') and the resource ('cache for a specific product by SKU'). It distinguishes from sibling tools like cache_purge_by_url and cache_purge_category by specifying the identifier type (SKU).

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 provides no guidance on when to use this tool vs alternatives such as cache_purge_by_url or cache_purge_category. There is no mention of when not to use it or what context is appropriate.

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