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

Beyond the annotations, it discloses the synchronous queue-and-wait behavior, typical latency (20-60s), the artifact's lifetime (public link, deleted after 24h), the failure modes (busy/rate-limit errors, validation errors with line-number prefixes), and that no separate validate tool exists. Annotations only say it is a non-read-only, non-idempotent, non-destructive local operation; the description supplies all the operational detail.

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?

Well front-loaded: the core behavior, return value, and error contract come first, with creative guidance last. It is long, and the script-format block is largely a verbatim duplicate of the same text embedded in the script parameter's schema description, which is redundancy 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 no output schema, the description carries the return-value burden and does so ('returns a public link to the MP4; the file is deleted after 24 hours') along with duration expectations and both failure shapes. For an 8-parameter, nested-object tool with a creative DSL, an agent has everything needed to call it correctly on the first attempt.

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 coverage is 100%, so the baseline is 3, but the description adds prescriptive guidance the schema does not: recommending speed 1.3-1.5, advising to omit scores/ages unless they matter (and noting they are invented plausibly), and explaining that nested replies and '> OP:' authorship drive the drama. It does restate the script grammar that already lives in the schema, which caps the score below 5.

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 specific verb and resource: 'Render a Reddit thread (script, or post+comments) to an MP4 and wait for it to finish.' It also distinguishes itself from the sibling reddit_screenshot (video vs. still) and from chat_render_video by the thread/script domain. An agent can identify the tool without opening the schema.

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 states the two mutually exclusive input paths (script vs. post+comments) and identifies both alternatives explicitly ('use this OR script, not both'), and it tells the agent there is 'no separate reddit_validate tool' so validation must be done by calling this and reading errors. What it lacks is a direct routing statement against reddit_screenshot for the still-image case.

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