Routine

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

No annotations are provided, so the description carries full burden. It mentions the tool creates a task (implying mutation) and gives parameter warnings, but doesn't disclose behavioral traits like required permissions, whether creation is reversible, rate limits, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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 with zero waste. The first sentence states purpose and primary usage, the second gives critical warnings. Every word earns its place, and the most important information is front-loaded.

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 creation tool with no annotations, no output schema, and a complex nested parameter structure, the description is incomplete. It provides good usage guidance but lacks behavioral context, return value information, and comprehensive parameter explanations. It's minimally adequate given the complexity.

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?

With 0% schema description coverage, the description compensates by specifying that 'Usually you only need to pass the title' and warns against using integration_id or distant_task_id. This adds meaningful guidance beyond the complex schema, though it doesn't explain other parameters like notes, occurrence, parent, etc.

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 ('a task'), and specifies it's simplified for MCP. However, it doesn't explicitly distinguish this from sibling tools like taskUpdate or taskComplete, though the 'simplified' hint suggests differentiation.

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 provides explicit guidance on when to use this tool ('Usually you only need to pass the title') and when not to use it ('Do not try to pass the integration_id or distant_task_id'). This gives clear usage boundaries despite not mentioning specific sibling alternatives.

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