cache_purge_category

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

No annotations are provided; the description only states the action without disclosing side effects, authorization needs, rate limits, or what happens to the cache. The generic input schema adds to the opacity.

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 concise sentence with no superfluous words. However, it is too brief to be fully informative.

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 tool's complexity (a simple purge that likely requires a category identifier) and lack of output schema, the description is incomplete—it does not explain input format, success behavior, or differentiate sufficiently from sibling purge tools.

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 100% coverage for a single 'params' object, but the description adds no additional meaning—it does not explain how to specify the category within params. Baseline 3 is reduced because the description fails to leverage the opportunity to clarify the parameter's purpose.

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 'purge' and resource 'cache for a specific category', distinguishing it from sibling tools like cache_purge_by_url and cache_purge_product. However, it lacks detail on what constitutes a 'category' identifier.

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, nor does it mention prerequisites (e.g., needing a category ID) or exclusions.

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