Create survey

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

The description adds value beyond annotations by naming the specific API method (add_survey) and clarifying that authentication is handled automatically. Annotations already indicate readOnlyHint=false and openWorldHint=true, so the mutation is expected. No contradictions.

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 two sentences with no fluff. It front-loads the purpose and adds essential context about the API and authentication. Every sentence 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?

Given the complexity of the LimeSurvey tool set and the presence of an output schema (not shown here), the description is adequate for a straightforward creation tool. It covers the key behavioral aspect (automatic auth) and purpose, though it could mention that the survey starts inactive or note next steps.

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 100%, so the parameters are well-documented in the schema. The description does not add additional meaning or context to the parameters beyond the schema, meeting the baseline.

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 verb (create) and resource (empty survey), and the title 'Create survey' reinforces it. Among many sibling tools like import_survey, copy_survey, and list_surveys, this tool is uniquely distinguished as creating a new empty survey with minimum settings.

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 mentions authentication details ('do not provide a session key') which is helpful, but it does not explicitly guide the agent on when to use this tool vs alternatives like import_survey or copy_survey. The context of 'minimum settings' is implied but not compared to other creation methods.

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