Assign an installed theme to a survey

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

Annotations already provide idempotent and non-destructive hints. The description adds value by clarifying that the tool works through set_survey_properties and does not install theme packages. This extra context about the underlying mechanism and scope enhances transparency beyond 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 a single, concise sentence that efficiently conveys the tool's purpose and a key limitation (no upload/install). Every word serves a purpose with no redundancy.

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 tool mutates survey state, the description lacks details on return values, error conditions, prerequisites (e.g., theme must exist), and the effect of confirm_theme_assignment. While annotations provide some context, the description is insufficient for a complete understanding.

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 67%, with survey_id lacking a description. The description does not add any parameter-specific meaning, missing the opportunity to clarify the purpose or format of the parameters beyond the 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 tool assigns an already imported theme to a survey, using the verb 'assign' and specific resource. It distinguishes from sibling tools like limesurvey_set_survey_properties and limesurvey_list_installed_themes by clarifying it does not upload or install the 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 theme must be already imported, but does not explicitly state when to use this tool versus alternatives such as limesurvey_set_survey_properties. No direct comparison or when-not conditions are provided, making the guidance adequate but not explicit.

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