List Remotion templates

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds the scope 'public' (vs private templates) and the filtering behavior 'optionally filtered by aspect ratio', which is useful context beyond the annotations. No additional behavioral details (e.g., return format, pagination) are given, but given the strong annotation coverage, this is adequate.

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, concise sentence that front-loads the main action ('List public templates') and appends the optional filter. Every word contributes meaning, with no fluff or repetition of the tool name or schema.

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 read-only listing tool with one optional parameter and strong annotations, the description is largely sufficient. It communicates the core functionality and the only parameter's purpose. It does not describe return value structure or pagination, but these are not essential given the tool's simplicity and the lack of an output schema. Minor gaps remain but the description is effective in context.

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 provides an enum for 'aspect' but no descriptions. The description explains that 'aspect' is an optional filter, which clarifies the parameter's purpose. However, it does not describe the meaning of each enum value (e.g., '9:16' means vertical), relying on the schema's enum list alone. Since there is only one parameter and the description gives the key semantic context, it meets the baseline but does not go beyond.

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 the verb 'List' and the resource 'public templates', with an optional filter by aspect ratio. It unambiguously distinguishes from sibling tools like get_template (which fetches a single template) by indicating a list operation.

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 this tool is for browsing available templates, especially when one wants to see templates matching a specific aspect ratio. However, it does not explicitly state when to prefer this over get_template or other sibling tools, leaving the choosing criteria implied rather than explicit.

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