Generate a responsive LimeSurvey survey theme

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

With annotations providing only false hints, description adds behavioral context: it creates a validated theme, inherits a specific base theme, and targets specific LimeSurvey versions. It does not fully disclose all side effects (e.g., overwrite behavior, authentication needs) but provides more than the annotations alone.

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, focused sentence of 18 words, effectively front-loading the purpose and key details without extraneous text. Every word earns its place.

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?

While the output schema exists, the description does not explain how parameters influence the generated theme, nor does it describe the generation process or return value. Given the high parameter complexity, the description is incomplete for guiding an agent on tool invocation.

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 very low (13%), yet the tool description does not mention any of the 23 parameters. It fails to add meaning beyond the schema, leaving parameter roles and guidance entirely to the schema's sparse descriptions.

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?

Description clearly states the tool creates a validated GPL-2.0-or-later ZIP theme inheriting Bootstrap 5 vanilla for LimeSurvey 7 or 6. It specifies verb (create), resource (ZIP theme), and distinguishes from sibling tools like validate_survey_theme or 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?

Description provides context on what the tool creates and for which versions, implying usage for theme generation. However, it does not explicitly state when to use this tool versus alternatives like limesurvey_validate_survey_theme or limesurvey_assign_survey_theme, nor provides when-not-to-use guidance.

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