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

Annotations supply only destructiveHint=true, which is oddly weak for a create operation, so the description carries most of the burden. It does add a real behavioral fact — that a project_id target routes into that project's 'Default Task List' — but says nothing about permissions, side effects, or what is returned.

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 short clauses plus an endpoint reference; the targeting distinction is front-loaded and nothing is padded. The trailing 'Paymo: POST /api/tasks' is low-value for an agent but costs little.

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 9-parameter mutation tool with no output schema, the description covers the key call-time decision (where the task goes) but leaves the agent without any sense of the response or post-creation state. It is minimally adequate given the fully populated schema, but not rich.

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 100%, so all nine parameters are already documented and parameter descriptions (including the project_id fallback rule) largely duplicate what the description says. The only genuinely additive detail is the destination 'Default Task List' behavior, which is not in the schema.

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?

States a specific verb and resource ('Create a task') and clarifies it can land in a task list or a project, which separates it from the read/update task siblings. It does not explicitly name or contrast against other create tools (create_project, create_time_entry), so it stops short of 5.

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 a routing rule between the two mutually exclusive targeting parameters (tasklist_id vs project_id), which is useful implied guidance for calling it correctly. However there is no when-to-use/when-not-to-use framing against sibling tools and no prerequisites stated.

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