create_task

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

Annotations already indicate that this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false), but the description adds no behavioral context beyond the name itself. No information about permissions, required relationships, or side effects is provided.

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?

While 'Create task' is concise to the point of being minimal, it is under-specified rather than appropriately concise. It provides no value beyond the tool name and does not earn its place.

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 create operation with 15 parameters, no output schema, and no explanation of return values or relationships to other entities, this description is severely inadequate. It lacks any contextual information that would help an agent invoke the tool correctly.

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 schema has 15 parameters with only 40% description coverage, and the description 'Create task' does not clarify any parameter meanings. It fails to compensate for the gaps in schema descriptions, leaving agents to guess at most fields.

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 'Create task' merely restates the tool name and title, providing no differentiation from sibling tools like update_task, delete_task, or list_tasks. It is a tautology rather than a meaningful purpose statement.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, expected context, or exclusions such as when to use update_task instead.

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