Create a copy of an existing survey with all its questions, styles, logic, and screens. Returns the new survey details including share_url.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Optional title for the copy (defaults to 'Original Title (Copy)') | |
| survey_id | Yes | The survey ID to duplicate |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states that all questions, styles, logic, and screens are copied and that the new survey details are returned, including share_url. This adds behavioral context beyond the annotations (which only indicate it's not read-only and not destructive) without contradicting them.
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 concise sentences, front-loaded with the action verb and purpose. It avoids redundancy and includes the key return value without unnecessary detail.
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 simple duplication tool with a well-documented schema, the description covers the core functionality and return value adequately. It does not mention error handling or prerequisites, but these are not critical for this straightforward operation.
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 coverage is 100%, with both 'survey_id' and 'title' described in the schema. The description does not add additional parameter semantics beyond what the schema provides, so it does not exceed the baseline for high coverage.
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 uses specific verb 'Create a copy' and identifies the resource as an 'existing survey', clearly distinguishing it from create_survey for new surveys. It also lists what is copied (questions, styles, logic, screens), leaving no ambiguity about its function.
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 gives clear context that this is for duplicating an existing survey, which is sufficient for an agent to infer when to use it. It does not explicitly mention alternatives or when not to use it, but the sibling tools make the distinction obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: surveys, responses, webhooks, analytics, and media library. Verbs like create, get, update, delete, list, and submit are applied clearly. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern (e.g., create_survey, list_responses, update_webhook). Naming is uniform and predictable, with no mixed conventions or vague verbs.
15 tools is well-scoped for a survey platform, covering surveys, responses, webhooks, analytics, and media. Each tool serves a unique purpose, and the count is within the ideal 3-15 range, not feeling bloated or thin.
The tool surface covers full CRUD for surveys and webhooks, response submission and retrieval, analytics, and media listing. Minor gaps exist (no media upload, no response delete), but core workflows are complete and agents can achieve common tasks without dead ends.
