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

Far exceeds the annotations, which only declare it is a non-idempotent, non-destructive write. The description adds externally-visible behavior: responses are stored with source 'external', technical data is set server-side and excluded from input, duplicate PersonalizedID causes failure, and the call performs a readback that costs one heavy-class request and requires a PersonalizedID to address the response.

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?

Well front-loaded — the external-source framing leads, followed by prerequisites, item structure, and failure/readback behavior. It is on the long side and partially re-states the nested items/personalizedID semantics already documented in the schema, but every sentence still carries information.

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?

With an output schema present, return values need not be explained, and the description goes further by stating that the reply reports stored data rather than mere acknowledgement. Prerequisites and failure modes are covered; the only minor gap is that no auth/permission requirements are mentioned, though annotations cover the safety profile.

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 baseline is 3, but the description adds real meaning beyond the schema: question variables must come from get_survey, PersonalizedID is optional on create yet required for readback (and required on update), and isCompleted semantics are restated with server-set completion date. It does not add syntax detail for code/value 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?

States a specific verb and resource (creates a new response/result case in a survey) and immediately scopes it to responses collected outside the survey link, explicitly contrasting them with link-submitted responses. An agent can distinguish this from get/list/update_survey_response without opening a schema.

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?

Gives concrete when-to-use cases (paper questionnaire, phone/in-person interview, import from another system) plus the precondition that publication must be started. It also routes the agent to the alternative explicitly: if a PersonalizedID already exists the call fails, and update_survey_response should be used to modify.

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