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

With the annotation readOnlyHint=true already signaling a safe read, the description adds value by disclosing that the response includes the full scenes/layers payload. This gives the agent useful expectations about the returned data beyond what the annotation provides.

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 a single, highly efficient sentence that front-loads the action and object ('Fetch a single custom template') and adds the key return detail ('including the full scenes/layers payload'). Every word earns its place.

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 single-parameter retrieval tool with readOnlyHint=true and no output schema, the description is complete. It explains what the tool does, what parameter it needs, and what the response will contain, leaving no critical gaps.

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?

The input schema has full parameter coverage: templateId is described as 'Template id (tpl_...).' The description does not add much beyond restating 'by id', but since the schema already handles the parameter meaning, the baseline 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 a specific verb ('Fetch') and resource ('single custom template') with a precise scope ('by id'). This distinguishes it from sibling tools like quiz_video_list_templates, which presumably fetch multiple templates without an id.

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 tool is for retrieving one specific template when you have its ID, providing clear context. It does not explicitly mention alternatives or exclusions, but the 'by id' phrasing makes the usage scenario unambiguous.

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