run_render

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

With no annotations, the description must carry the behavioral disclosure burden. It does disclose that the tool runs a job and returns an exit code and output probe summary, which is useful. However, it omits side effects like file overwriting (the overwrite parameter hints at this), long-running behavior, failure behavior for missing jobs, or safety/idempotency characteristics. The description provides basic behavioral information but not comprehensive transparency.

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 sentence that front-loads the action ('Run') and resource, then states the output. There is no filler, tautology, or wasted words. It is an appropriately sized and well-structured description.

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?

This tool has 3 parameters with zero schema descriptions and no annotations. While an output schema exists and may document return values, the description is too sparse for an agent to call this correctly in a real context. It fails to explain prerequisites (the job must already be set), parameter semantics, or failure modes. For a non-trivial execution tool, this leaves too much unspecified.

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 0%, so the description must compensate for parameter meaning. It only loosely implies job_id via 'previously defined render job'. It says nothing about overwrite or allow_any_path, their defaults, or when to use them. An agent cannot deduce what overwrite=true means or when allow_any_path should be set, which is a critical gap.

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 states a specific verb ('Run'), a specific resource ('previously defined render job'), and the result ('exit code + output probe summary'). This clearly distinguishes it from set_render_job (which defines jobs) and run_ffmpeg (which runs arbitrary ffmpeg commands), so an agent can tell what this tool does without confusion.

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 phrase 'previously defined render job' implies the tool should be used after set_render_job, but it does not explicitly say that. No alternatives are named, and no conditions or exclusions are provided. The usage guidance is implied rather than explicitly stated.

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