runrunit_create_task

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

With no annotations, the description carries the full burden. It explains the default board, column, assignee behavior, and the special handling of the description parameter (appended via Task Description API, never replacing existing text). This adds useful context beyond basic creation, though it does not mention rate limits or auth requirements.

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 efficient paragraph that starts with the core purpose, then required fields, then optional ones. Every sentence adds value, and there is no wasted text.

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 no output schema, the description omits return value details (e.g., whether the created task object is returned). However, it covers defaults, parameter behavior, and optional fields thoroughly. The 'etc.' at the end is slightly vague but acceptable.

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 description coverage is 100%, but the tool description adds significant meaning: it explains default values (board, column, assignee), the title format hint, and the appending behavior for description. This goes far beyond mere schema 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 verb 'Create' and resource 'task', specifies default board (Ongoing with ID 96356), default column (Task), and default assignee (the caller). This distinguishes it from sibling tools like runrunit_update_task and runrunit_delete_task.

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 lists required fields (title, type_id) and optional ones, giving an example title format. It implies the tool is for creating tasks in the specified default board/column, but does not explicitly say when not to use it or mention alternatives for other boards (though no other create task tool exists among siblings).

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