Generate a professional survey using AI based on a research goal. Returns the survey ID and shareable link.
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | Describe what you want to research. E.g. 'Customer satisfaction survey for our SaaS product after onboarding' | |
| lang | No | Language for the survey content. Defaults to 'en'. | |
| publish | No | Whether to immediately publish the survey after creation. Defaults to false. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It states it creates a survey and returns ID/link, but does not disclose side effects, permissions, or safety profile. Adequate but minimal.
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?
Single sentence, front-loaded with purpose. No filler words, highly efficient.
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 simple schema and no output schema, the description explains return values (ID and link). Could mention AI generation aspect but overall complete for a creation tool.
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%, so the description adds no extra parameter meaning beyond what the schema already provides. Baseline score of 3 is appropriate.
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 'Generate a professional survey using AI' which is a specific verb-resource combination. It distinguishes from sibling tools like get_surveys (listing) and get_responses by implying creation.
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 usage when a new survey is needed, but does not explicitly state alternatives or when not to use. Still, context from siblings makes it clear enough.
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.
Tools have distinct purposes, but create_survey and get_survey_link both involve shareable links, causing slight overlap. Otherwise clearly differentiated.
All tools follow a consistent verb_noun pattern using snake_case, e.g., create_survey, get_responses, publish_survey.
Six tools are well-scoped for a survey management server, covering creation, listing, publishing, and data retrieval without being excessive.
Core survey lifecycle is covered (create, publish, list, get responses, report), but missing update and delete operations are minor gaps.