Show LiteSpeed Cache status

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavioral detail beyond 'show' — such as whether the cache status can be unavailable, what values may appear, or whether any plugin dependency exists. This is acceptable but not deeply transparent.

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 short, focused sentences with no filler. The core purpose is front-loaded, and the additional guidance about obtaining the software identifier is placed where it is most useful.

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?

For a simple read-only status tool, the description covers the target resource and how to find the key identifier. However, the required `username` parameter is not contextualized, and with no output schema, the description does not indicate what the status response looks like.

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 the baseline is 3. The description adds helpful meaning for `software` by pointing to GET /api/hosting/v1/wordpress/installations and the `id` field, but it leaves `username` essentially unexplained beyond the schema's tautological 'username parameter'.

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 states a specific verb ('Show') and a precise resource: the LiteSpeed Cache status for a specified WordPress installation. This clearly identifies which operation is being exposed and distinguishes it from related siblings like purgeLiteSpeedCacheV1 or showMemcachedObjectCacheStatusV1.

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 gives clear context: use this tool to check LiteSpeed Cache status for a particular WordPress installation, identified via the software parameter. It does not explicitly list alternatives or exclusions, but the target use case is unambiguous enough for an agent to select it correctly.

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