create_task

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

With no annotations, the description must disclose behavioral traits. It only states 'Create a new task' without mentioning required permissions, duplicate handling, side effects, or return values. Critical context like the need for a valid boardId or what happens on failure is absent.

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, front-loaded sentence that efficiently states the tool's purpose. While it lacks detail, it avoids extraneous text. It could benefit from more structure, but it is not verbose.

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 the tool's complexity (nested schema, many parameters, no output schema, no annotations), the description is severely incomplete. It does not cover prerequisites, return structure, or parameter details, leaving significant gaps for the agent.

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?

The input schema has many sub-parameters with 0% description coverage. The description adds no meaning beyond field names, failing to explain what 'groupId', 'milestones', or 'followers' represent. The agent must guess their purpose from context alone.

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 action ('Create'), the resource ('a new task'), and the context ('in the Vaiz workspace'). This verb+resource+location pattern effectively distinguishes this tool from siblings like 'create_milestone' or 'edit_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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that editing existing tasks should be done via 'edit_task', or that creating comments uses 'create_task_comment'. The agent gets no context for tool selection.

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