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 behavioral burden and delivers none of it. It does not state permissions required, side effects, whether the created task is linked to anything, or what happens on failure.

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 short sentence is not verbose, but it is under-specified rather than concise — it earns its place only by naming the operation. There is no front-loaded detail because there is no detail at all.

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 mutation tool with no annotations, no output schema, an opaque nested 'body' parameter, and many overlapping siblings, the description is completely inadequate. An agent has no basis 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 single required parameter 'body' is a free-form nested object with additionalProperties {} and 0% schema description coverage, and the description says nothing about its expected keys or shape. With zero coverage and a nested object, the description must compensate and does not.

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 a task' merely restates the tool name and title with no additional specificity. It states a verb and resource, but does not distinguish this tool from siblings like add_request_task or create_change, nor does it clarify scope (e.g., where the task is created or what a task is here).

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?

There is no guidance whatsoever on when to use this tool versus alternatives. Siblings such as add_request_task and create_change overlap conceptually, and nothing in the description helps an agent choose.

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