add_task

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

With no annotations provided, the description must disclose behavioral implications, but it only restates the core action of adding a task. It does not mention permissions, side effects, how the task is scoped, or whether existing tasks or groups are affected.

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 single sentence is concise, but it is not appropriately sized because it omits essential parameter and scoping details. The ambiguous 'group/personal' phrasing also reduces clarity rather than adding precision.

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 nested task_data object, required zgid parameter, and no schema descriptions, this one-line description is insufficient for correct invocation. An agent cannot determine required task fields, the group/personal distinction, or how zgid should be used.

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 0%, and the description never mentions zgid or task_data. Because task_data is an unconstrained nested object, the lack of any parameter guidance leaves the agent without enough information to construct a valid payload.

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 names the verb 'Add' and the resource 'task', and it distinguishes this creation action from the task-related siblings that get, update, or delete tasks. However, the 'group/personal' qualifier is ambiguous and does not explain how the two variants are selected.

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, when a task counts as 'group' vs 'personal', or what the required zgid parameter represents. The description does not mention any exclusions or preconditions.

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