add_render_job

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it adds to the queue and returns a job ID, but does not disclose whether the action is asynchronous, if the queue has limits, or if any prerequisites (e.g., open project) are required.

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 sentence that front-loads the action and result. Every word is necessary and there is no filler.

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 tool with no parameters and no output schema, the description is short but lacks context. It does not explain how the returned job ID can be used (e.g., with 'get_render_job_status') or the relationship with other tools like 'start_render'. Adequate for a simple action but with gaps.

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?

There are no parameters, and the schema coverage is 100% trivially. The description adds no additional meaning beyond the schema, which is empty. Baseline of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action: adding current render settings to the render queue and returning the job ID. It distinguishes from siblings like 'set_render_settings' (which sets settings) and 'start_render' (which may start rendering directly), as it focuses on queuing the job with existing settings.

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 implies that the tool should be used after setting render settings and before starting the render, but it does not explicitly state when to use or avoid it compared to alternatives like 'start_render' or 'render_to_file'. No exclusions or context are provided.

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