Get Remotion template

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is clear. The description adds the qualifier 'public' which suggests it only works on public templates, but discloses no other behavioral traits such as return format or rate limits. This 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?

The description is a single, front-loaded sentence with no fluff. It states the action and the object efficiently, which is ideal for a simple getter tool.

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 one-parameter tool with no output schema, a bit more context is needed. The term 'contract' is not defined, and there is no hint about the return value structure or typical usage. Sibling tools might clarify, but the description alone is somewhat incomplete for a new agent.

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 description coverage is 0%, and the description does not mention the templateId parameter or its allowed values. The enum in the schema provides some meaning, but the description does not help clarify what the template IDs represent or how they relate to the contract. This leaves the agent with insufficient info to select a correct value confidently.

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 uses the specific verb 'Get' and identifies the resource as 'one public template contract', distinguishing it from list_templates which retrieves multiple. However, the term 'template contract' is somewhat jargon and not fully explained, slightly reducing clarity.

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 does not provide any guidance on when to use this tool over alternatives. It does not mention that templateId is required, nor does it reference sibling tools like list_templates or get_video_schema. A comparison or usage scenario would be helpful.

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