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

Annotations only mark it as a non-idempotent, non-destructive, non-open-world write. The description adds substantial behavior the agent cannot get elsewhere: the render is queued and awaited, it returns only on completion/failure/timeout, typical latency is 20-60s, output is a public link whose file is deleted after 24 hours, and rate-limit/busy conditions surface as errors with a message. That is exactly the kind of disclosure annotations do not carry.

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?

Purpose, timing, and return-value caveats are correctly front-loaded in the opening sentences. The bulk of the description is a script-format block that largely duplicates the script parameter's schema description, which is redundant weight rather than new information.

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?

With 13 parameters (including nested objects) and no output schema, the description appropriately compensates by describing the return value (public MP4 link, deleted after 24h) and failure modes. Parameter-level detail is delegated to a fully covered schema, so an agent has what it needs to call the tool 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 baseline is 3. The description re-explains the script format, but that text is essentially duplicated from the script parameter's own schema description, so it adds little beyond the structured field; the other twelve parameters (speed, theme, platform, statusBar, etc.) get no additional semantic framing in the prose.

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 first sentence gives a concrete verb+resource+output: 'Render a txtreel conversation (script or messages) to an MP4 and wait for it to finish.' That is unambiguous and clearly a video-render tool, implicitly distinct from chat_screenshot. It never names its siblings (chat_screenshot, chat_validate, reddit_render_video), so it stops short of full differentiation.

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?

It conveys operational context (queues then waits, 20-60s for a short render, errors on busy/rate limit) and states 'use this OR messages, not both,' which is useful guidance. However it never says when to prefer this over chat_screenshot or chat_validate, nor any when-not conditions, so usage is only implied.

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