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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behaviour, so the safety profile is fully covered. The description adds only that the payload is the template's questions and settings, which is modest and partly redundant given an output schema exists; no pagination, size or error behaviour is mentioned.

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?

Two tight sentences: the purpose and decision context come first, with the ID provenance as a trailing hint. Nothing is wasted or padded.

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 one-parameter read tool with full schema coverage, rich annotations and an output schema, the description supplies everything an agent needs to pick it and call it correctly.

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% for the single templateId parameter, so the baseline is 3. The description does add provenance value by naming template_list_top_suggested alongside the two sources the schema lists, but it offers no format or validity detail beyond that.

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 ('Read one template's questions and settings') plus the intent behind the read ('to check it fits before creating a survey'), which separates it cleanly from template_list, template_lookup and template_create_survey_from.

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 clear context for use (pre-flight check before creating a survey) and names the upstream tools that supply the ID, so the agent knows the ordering. It does not explicitly say when to skip this tool and go straight to template_create_survey_from, which keeps it short of a 5.

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