Purge LiteSpeed Cache

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Purge the LiteSpeed Cache' without explaining side effects (e.g., cache is cleared, site performance impact), required permissions, or what the result is. This is insufficient for a mutation operation.

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 fluff or redundant information. It effectively communicates the core purpose in minimal words, though it lacks additional structured guidance.

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 is a cache purge with no annotations and no output schema, so the description must provide more context. It omits critical details like whether the purge is site-specific or server-wide, the impact on the site, and how it relates to sibling tools. This is insufficient for an agent to safely invoke it without further assumptions.

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 100% for the two parameters (username, software), both with clear descriptions. The tool description adds no additional meaning beyond the schema, meeting the baseline but providing no extra value.

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 a specific verb ('Purge') and resource ('LiteSpeed Cache'), which distinguishes it from tools like wp_litespeed_status. However, it doesn't specify whether this purges all LiteSpeed caches or just for a specific site, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives such as hosting_cache_clear or wp_litespeed_status. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction on tool selection.

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