render_title_card

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

With no annotations, the description carries the full burden and does well: it discloses the output container/codec (ProRes 4444), transparent background, animation behavior, and crucially that it returns a preview IMAGE. It omits any permission/overwrite caveats, but for a render-to-file tool that is minor.

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?

Four tight sentences that are well front-loaded: what it produces first, then return value, then placement workflow. Dense but every sentence carries actionable information with no padding.

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 13-parameter tool with no output schema, the description compensates by explaining the deliverable, the preview-image return, and the sequencing constraints. Parameter-level detail is left to the fully-covered schema, so overall it is complete enough to call correctly.

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 100%, so every parameter is already documented with defaults, ranges, and enums in the schema. The description reinforces intent (match width/height/fps, title vs subtitle, slide/fade) but adds little syntax or meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (renders) and resource (animated title card with channel name/subtitle), plus the exact output (.mov, ProRes 4444, transparent background) and its intended use (intros, section titles). An agent can immediately distinguish this from siblings like add_text_overlay.

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?

Gives a clear downstream workflow (import with import_media, place with add_to_timeline above footage) and names the config source (get_sequence_settings). It establishes context strongly but does not state when NOT to use it or contrast with alternative text-creation siblings such as add_text_overlay.

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