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

Goes beyond the annotations by explaining the retry contract ('Reuse use.requestId for retries of the same intended draft'), that the template is left unchanged, and that research does not start. The annotations already flag idempotentHint=true and non-destructive behavior, so this confirms and enriches rather than merely restates, though it omits permission/authorization requirements.

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?

Three tight sentences with the mutation front-loaded, followed by retry semantics and side-effect clarifications. No filler, though a brief pointer to the relevant sibling would have added value without bloat.

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?

An output schema exists, so return values need not be described. The description covers the mutation's scope, idempotency/retry behavior, and non-effects ('template is unchanged', 'research does not start'), which is strong for a nested-parameter write tool; only permission/auth requirements are absent.

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?

With only 50% schema description coverage, the description usefully explains the meaning of both nested fields—expectedRevision as the template revision being acted upon and requestId as a retry-deduplication key. It compensates well for the coverage gap, though templateId itself is left to the schema and obvious naming.

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 an independent editable Study draft') plus the source ('from a readable template at use.expectedRevision'). This makes it clearly distinguishable from siblings like create_study (blank study) and duplicate_study (copying an existing study), without needing to name them.

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 the workflow context ('Fresh context and Audiences are added in the web app; the template is unchanged and research does not start') but never states when to choose this over create_study, duplicate_study, or list_study_templates. Usage is inferable but not explicit, and no exclusions are given.

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