resolve_start_render

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action without indicating whether rendering runs asynchronously, whether the tool blocks until completion, any side effects on the render queue, or what the return value contains. Sibling tools like resolve_wait_for_render and resolve_get_render_status imply these aspects, but the description fails to mention them, leaving significant unknowns for an agent.

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, concise, front-loaded sentence with no filler. Every word earns its place, making it easy to parse quickly. It is appropriately sized for a parameterless action.

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?

The tool is simple and has an output schema (though not shown), but the description omits important workflow context. It does not explain that after starting a render, an agent should use resolve_wait_for_render to await completion or resolve_get_render_status to monitor progress. Given the sibling ecosystem, this omission leaves the description incomplete for an agent planning a multi-step rendering workflow.

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?

The tool has zero parameters, so the description has no parameter burden to carry. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate even though no parameter-specific details are added. The schema already covers everything (vacuously).

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 'Start rendering all queued render jobs' uses a specific verb and resource, clearly distinguishing this from sibling tools like resolve_add_render_job (which adds a job) and resolve_get_render_status (which queries status). It is not a tautology and leaves no ambiguity about the intended action.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., that render jobs must be queued first), the need to call resolve_wait_for_render afterward, or the relationship to resolve_get_render_status. An agent would not know the proper workflow sequence from this description.

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