yougile_create_task

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

Annotations already indicate a write operation (readOnlyHint=false) that is not destructive. The description adds valuable behavioral context: columnless tasks are nested under a parent and do not appear as board cards. It doesn't cover auth/reversibility, but the annotations cover the core safety profile.

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, front-loaded with the core action, followed by a compact enumeration of supported fields. Every word earns its place, and the structure is scannable for an agent.

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 tool is complex (10 params, nested objects, no output schema), and the description does a strong job covering the two operational modes and the supported feature set. However, it doesn't mention what the tool returns (e.g., created task ID or object), which is needed since no output schema exists.

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%, so the schema already documents all 10 parameters in detail. The description recaps parameter names and some values (e.g., color enum) but adds no significant new semantics beyond what the schema provides.

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 starts with 'Create a new task' — a specific verb + resource — and immediately differentiates board tasks from columnless subtasks. This clearly distinguishes it from sibling create_* tools (create_column, create_project, etc.) and from update_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?

It explicitly instructs when to provide columnId (to place on a board) and when to OMIT it (to create a columnless subtask), then links via the parent's subtasks. This gives the agent unambiguous guidance for both usage modes.

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