create_task

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only mentions priority constraints and says 'Create a new task', but does not disclose return values, required permissions, side effects, or failure modes. This is a significant gap for a mutation tool.

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 concise, two sentences, with no filler. It leads with the verb and resource, and the second sentence adds the priority enum. Every word earns 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?

With 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, due_date format, tag behavior, or error conditions. An agent would have to guess at important invocation details, making the description inadequate for correct tool use.

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%, so the description must compensate. It only documents the valid values for 'priority', but does not explain the format or semantics of 'due_date', 'tags', or the required fields. The parameter names are self-explanatory but the description adds little beyond what the schema already 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 uses the specific verb 'Create' with the resource 'task', clearly indicating the action. The sibling tools are all different operations (update, get, list, search, overdue), so there is no ambiguity. It also provides valid priority values, adding specificity beyond the schema.

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 usage is implied by the verb 'create' and the resource 'task' — an agent would understand to use this when creating a new task. However, there is no explicit guidance on when not to use it or how it relates to sibling tools, though none of the siblings perform creation.

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