Create task

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

Annotations already reveal this is a non-readonly, non-idempotent write. The description adds key context that no duplicate detection occurs, which is non-obvious and useful. It does not explain return value or permissions, but the core behavioral caveat is disclosed.

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 short sentences with a clear lead action and one essential caveat. No filler or repetition of schema details; every word adds value.

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 simple three-parameter creation tool with no output schema, the description covers purpose, usage, and a critical edge case. It could mention what is returned or that the task is immediately placed on the board, but the provided information is sufficient for safe invocation.

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 all parameters are already well-documented with descriptions and defaults (tags, title, status). The description adds no additional parameter semantics, so baseline 3 is appropriate.

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?

States a specific action and resource: 'Add a task to the board.' This clearly distinguishes create_task from sibling search_tasks and set_status, and the dedup warning reinforces that it is a creation operation.

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?

Explicitly instructs the agent to search first because the tool does not detect duplicates, effectively telling when to use search_tasks before invoking create_task. This gives clear behavioral guidance for avoiding duplicate creation.

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