import_group

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Import') which implies a write operation, but doesn't clarify permissions needed, whether it's idempotent, what happens on failure, or the expected output format. This leaves significant gaps for a mutation tool with zero annotation coverage.

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 appropriately brief with a clear opening sentence followed by parameter explanations. Each sentence adds value, though the parameter section could be more integrated with the main description rather than presented as a separate 'Args' block.

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 mutation tool with 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what constitutes a 'group' in LimeSurvey, what the import process entails, what format the group file should be in beyond base64 encoding, or what the tool returns upon success/failure.

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 description lists all three parameters with brief explanations, adding meaning beyond the 0% schema description coverage. It clarifies that 'group_file' should be base64 encoded and 'group_name' is for the imported group. However, it doesn't explain what a 'group' is in LimeSurvey context or provide format details for the file content, leaving some ambiguity.

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 action ('Import a group') and the target resource ('to a LimeSurvey survey'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from similar sibling tools like 'import_survey' or 'import_question', which would require more specific context about what a 'group' represents in LimeSurvey.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing survey), exclusions, or how it differs from sibling tools like 'add_group' or 'import_survey', leaving the agent to infer usage context from the tool name alone.

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