List Mographr's free motion-graphics tools: customizable animated video templates (lower thirds, titles, intros, callouts) that render a real MP4. Each tool supports custom text, preset color schemes and multiple design systems. Free renders include a small mographr.com watermark; each tool's page offers an interactive editor.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds domain context about the listed tools (e.g., watermark and interactive editor), but it does not disclose behaviors of the list operation itself, such as pagination, sorting, or response format.
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 composed of two concise sentences. The first sentence front-loads the core purpose ('List...') and follows with a list of tool types, while the second adds valuable detail about customization, watermark, and editor. Every sentence 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 zero-parameter list tool with no output schema, the description gives a strong sense of what the returned catalog contains: template types, customization options, watermark policy, and editor availability. It lacks explicit return-format details but is adequate given the tool's simplicity.
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?
This tool has zero parameters, and the schema coverage is 100% (vacuously). The description correctly focuses on the catalog contents, and there are no parameter semantics to explain, so the baseline 4 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 opens with 'List Mographr's free motion-graphics tools', a specific verb + resource that clearly identifies the operation. It then elaborates on tool types and features, distinguishing this catalog-listing tool from siblings like get_motion_tool or render_motion_tool.
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 provides rich context that the tool is an overview of available free tools, including their features, watermark, and editor. However, it does not explicitly state when to use this instead of get_motion_tool or render_motion_tool, nor mention any exclusions, so it falls 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.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct role: listing available tools, fetching a tool's schema, initiating a render, and polling render status. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_motion_tools, get_motion_tool, render_motion_tool, get_motion_render. The verbs clearly indicate the action, and the nouns are consistent.
Four tools is well-suited for this server's scope—covering discovery, schema inspection, rendering, and polling. No tool feels redundant or missing.
The tool set covers the full workflow: list available templates, get detailed customization options, render a video, and retrieve the result. There are no obvious gaps for the stated purpose.