List installed LimeSurvey themes (best effort)

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by explaining the tool uses two non-official signals (generated_packages, themes_in_use) and warns about incomplete data. No contradiction with annotations.

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 front-loaded with the tool's purpose and uses two sentences to explain the signals and fallback. It is concise enough but could be slightly tighter; however, it earns its length by providing essential context.

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 (no official method) and the presence of an output schema (mentioned), the description does not need to explain return values. It covers the two data sources and the admin-UI fallback, making it complete for an agent to understand what the tool does and its limitations.

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 single parameter (survey_scan_limit) has 100% schema description coverage, including default, min, max, and description. The tool description does not add further semantics for this parameter, so baseline 3 is appropriate.

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 it lists installed LimeSurvey themes using best-effort signals, with a specific verb ('list') and resource ('installed themes'). It distinguishes itself from sibling tools (none of which list themes) and includes the 'best effort' qualifier to set expectations.

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 explains when to use this tool (when you need to enumerate installed survey themes) and mentions a fallback (admin-UI). It implies that this is a workaround due to lack of official method, but does not explicitly state when not to use or name alternatives beyond the fallback.

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