Validate a generated LimeSurvey survey theme

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

Annotations indicate read-only, idempotent, non-destructive behavior, and the description adds specific checks (e.g., 'manifest, licensing, archive paths, safe assets, responsive CSS, LimeSurvey 6/7 compatibility'). This provides behavioral context beyond annotations, though it could mention return details.

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 sentence that front-loads the main action. It lists multiple checks, making it slightly lengthy but still efficient. No redundant phrasing is present.

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 one required parameter and an output schema (assumed), the description covers the validation scope but omits prerequisites (e.g., theme must be generated) and error conditions. It is adequate but not fully complete.

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?

With schema description coverage at 0%, the description must explain the parameter. However, it only says 'Validate a ZIP inside LIMESURVEY_THEME_DIR' without linking to the 'file_name' parameter or specifying format requirements. The schema indicates a string with minLength 5, but the description adds no further meaning.

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 the specific verb 'Validate' and identifies the resource as 'a ZIP inside LIMESURVEY_THEME_DIR'. It lists exactly what is checked (manifest, licensing, etc.), clearly distinguishing it from sibling tools like limesurvey_generate_survey_theme and limesurvey_assign_survey_theme.

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 implies the tool is used after generating a theme and before assigning it, but it does not explicitly state when to use it or provide alternatives. There is no mention of when not to use it, such as if the theme is not generated yet.

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