create_task

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

With no annotations present, the description carries the behavioral disclosure burden and does well by explaining automatic project fallback, context inheritance, and parameter constraints like the 1024-character limit on descriptions and expected formats for due_date, priority, and status. It does not detail persistence guarantees or failure scenarios, but 'create' clearly signals mutation and the output schema covers return values.

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 efficiently front-loaded with the primary action and key behavioral nuance, followed by a clean, uniformly formatted Args list. Every line earns its place, and the structure makes scanning parameter semantics easy for an agent.

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?

The description covers all seven parameters, the active-focus fallback behavior, and relevant example values, while the presence of an output schema reduces the need to document return values. It could be more complete by specifying whether project names must pre-exist or how invalid due_date strings are handled, but it is sufficient for correct invocation.

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 0% description coverage, so the Args section is essential and fully compensates by explaining every parameter's purpose, optionality, formatting, and examples. This adds substantial meaning beyond the bare schema types and defaults.

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 opens with 'Create a new task', a specific verb-plus-resource statement that clearly identifies the tool's core function. It is readily distinguishable from task-focused siblings like update_task_status, complete_task, and cancel_task because it is explicitly about creation rather than modification or removal.

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 clear usage context, especially the automatic fallback to the active focus context when no project is specified, and notes that context inheritance is handled automatically. It does not explicitly state when not to use the tool or name alternatives, but the creation-focused language makes the primary usage scenario evident.

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