add_render_job

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

The description fails to disclose important behavioral traits. It implies a state change (adding to queue) but does not clarify if the addition triggers immediate rendering, whether the tool is idempotent, or if there are any side effects (e.g., on existing jobs). With no annotations provided, the description carries the full burden of disclosure, which is not met.

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 of appropriate length, front-loading the key verb and resource. Every word serves a purpose, with no redundancy or irrelevant details.

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?

Given the tool's simplicity (zero parameters) and the presence of an output schema (which reduces need to explain return values), the description is minimally adequate. However, in the context of many sibling tools with overlapping functionality, the description does not provide enough context about how this tool fits into the rendering workflow (e.g., sequential steps). A more complete description would note that render settings must be configured beforehand.

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 per rubric baseline is 4. The description does not add any parameter-specific meaning beyond the schema, but that is acceptable since schema coverage is 100%. No further clarification is needed for parameters.

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 ('add a render job') and the resource ('to the queue') with a condition ('based on current render settings'). This verb+resource+condition combination makes the purpose unambiguous. However, it does not differentiate from siblings like 'start_rendering' or 'set_render_settings', which might overlap in functionality.

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?

No guidance is provided on when to use this tool versus related siblings. The description does not mention prerequisites (e.g., need to set render settings first) or the typical workflow (e.g., after adding, one might need to start rendering). This omission leaves the agent uncertain about the correct usage context.

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