hosting_purgeLiteSpeedCacheV1

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

No annotations provided, so description carries full burden. It states the action is 'purge' (destructive), but gives no additional behavioral context (e.g., impact on performance, reversibility). This is adequate but minimal.

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 sentences, front-loaded with the action, no redundant words. However, could be even more concise by omitting the parameter retrieval sentence if the schema already describes it.

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 no annotations or output schema, the description covers purpose and parameter source but lacks information about expected outcomes, side effects, or post-purging behavior. It is functional but not comprehensive.

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%, so baseline is 3. The description adds value for 'software' parameter by explaining its source, but 'username' remains unelaborated. Overall, limited added meaning beyond schema.

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 'LiteSpeed Cache' for a WordPress installation, using a specific verb and resource. It distinguishes itself from sibling tools like hosting_clearWebsiteCacheV1 and hosting_showLiteSpeedCacheStatusV1.

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 guidance on obtaining the WordPress installation ID from another API (GET /api/hosting/v1/wordpress/installations), but does not explicitly state when not to use this tool or name alternatives like hosting_clearWebsiteCacheV1.

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