add_to_render_queue

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

The description is minimal, stating only the action without disclosing side effects (e.g., whether it starts encoding, handles duplicates, or requires prerequisites). Annotations are all false and don't compensate, so the description fails to adequately describe behavior.

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?

Single, front-loaded sentence with no extraneous words. Efficient and to the point.

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 two parameters, no output schema, and no annotations, the description is too brief. It omits important details like what happens after adding to queue, error states, or whether it's a fire-and-forget operation.

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?

Both parameters are documented in the schema with descriptions. The tool description adds no extra meaning beyond what the schema provides, meeting the baseline for 100% schema coverage.

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 uses a specific verb ('Add') and resource ('active sequence' to 'Adobe Media Encoder render queue'), clearly distinguishing it from sibling tools like 'start_batch_encode' or 'export_sequence' that handle encoding or export directly.

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 explicit guidance on when to use this tool versus alternatives. The purpose is clear but the description lacks any 'when-not-to-use' or comparison to siblings, leaving the agent to infer from context.

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