Update survey response

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

The description adds that it calls a specific LimeSurvey method and provides authentication instructions (use configured service account, no session key). However, annotations already indicate it's a write operation (readOnlyHint false, destructiveHint false), so the added behavioral context is modest.

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?

Two short sentences, front-loaded with the core purpose. The second sentence provides implementation and authentication context, which is relevant but slightly ancillary. Very efficient with no wasted words.

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 (nested object parameter, 3 parameters, output schema exists), the description covers the basics but omits behavior details like response format, success/failure indicators, or how partial updates work. The schema provides parameter details but the description could add more context for safe usage.

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 input schema already describes the response parameter as including the response ID (schema description: 'Response fields, including the response ID'). The description repeats this without adding further semantic value beyond what the schema provides.

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 'Update a response' with the verb 'update' and specifies the resource (response). It distinguishes from sibling tools like limesurvey_add_response and limesurvey_delete_response by using 'update' and mentioning the required response ID, which implies modification of an existing entity.

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 when to use (to update an existing response, by including its ID) but does not explicitly state when not to use or provide alternatives. No comparison with add or delete tools is given.

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