Run task

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

The description indicates it's a write operation ('kicks off a run'), consistent with readOnlyHint=false, but adds no additional behavioral context beyond what annotations already provide. No mention of permissions, side effects, or rate limits.

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?

Two sentences conveying purpose and API endpoint efficiently. Could be slightly more concise by omitting the API call, but still succinct.

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 description covers the basic action but does not mention what the response contains (e.g., task run ID or status). With no output schema, this omission reduces completeness for agent understanding.

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 coverage is 100%, so the description adds little beyond what the schema already explains. The description mentions 'passing the provided input data' but defers details to the schema's parameter descriptions.

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 tool initiates a run of a workflow task by providing the task ID and input data, and specifies the API endpoint. It distinguishes itself from sibling tools like render_get_task and render_list_tasks.

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 on when to use this tool versus alternatives, such as checking if the task exists first or noting prerequisites. The description assumes the agent knows when to invoke it.

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