Get template details

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

Discloses that the tool returns the full variable list and that variable names are case-sensitive, which aids behavior prediction. The readOnlyHint annotation is consistent, so no contradiction. No mention of rate limits or auth, but acceptable for a simple read tool.

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 sentences with zero waste. The critical information is front-loaded: what the tool does and why it's useful.

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 retrieval tool with one parameter and no output schema, the description fully covers purpose, usage, and return value implications. No gaps remain.

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% (templateId described). The description adds context beyond the schema: clarifies where to get the ID ('from list_templates or the STUDIO templates page') and emphasizes case-sensitivity of variable names, which is not in the schema.

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 'Retrieve a single Synthesia template by ID, including its full variable list.' This is a specific verb-resource combination and distinguishes from sibling tools like list_templates (listing) and create_video_from_template (using the template).

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?

Explicitly advises 'Call this before create_video_from_template to see exactly which templateData keys are expected,' guiding the agent on proper usage sequence. Does not explicitly mention when not to use it, but the context is sufficient for differentiation from list_templates.

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