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

Annotations already indicate readOnlyHint=false, so the description's mention of 'create' is consistent. It adds context about creating a draft (as opposed to a finalized survey) and identifies the template via flags. However, it does not disclose potential side effects or permission requirements, which is acceptable given the annotation coverage.

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?

A single, well-structured sentence that front-loads the key concept ('Create a new draft') and efficiently explains the template identification criteria. 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 tool's simplicity (3 parameters, no output schema), the description covers all necessary information for the agent to call it correctly: how to identify a template, what the resulting survey is (a draft), and parameters are fully described in schema. It does not over-explain but is complete enough.

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 baseline is 3. The description adds meaningful context by explaining that template_id refers to a survey with is_template=true, which clarifies the schema's terse 'Survey id of the template'. This extra context helps the agent understand the parameter's semantics more fully.

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 states a specific action ('create a new draft'), a resource ('copying a template survey'), and precisely defines what qualifies as a template via flags. It clearly distinguishes from create_survey (blank creation) and create_survey_from_question (creation from a question).

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 explains the prerequisite for using this tool (template marked with set_survey_template_flag, is_template=true) but does not explicitly contrast it with alternatives like create_survey or create_survey_from_question. The intended use is clear, but no exclusions are stated.

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