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

Annotations cover safety flags (destructive, openWorld, idempotent), and the description adds real behavioral context beyond them: only accepted values are saved, cancelling is a no-op, and successful creation may trigger notifications, webhooks and automation. The host-support requirement is also disclosed. No contradiction with the declared hints.

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?

Four front-loaded sentences with no filler; the core action leads and the constraints follow. Slightly long, but each sentence carries distinct operational information.

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 an interactive, form-eliciting mutation with no output schema and one undocumented parameter, the description covers mechanism, prerequisite, fallback tool, cancellation semantics, side effects, and the only input parameter. Nothing essential to correct invocation is missing.

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 coverage is 0% with a single optional projectId. The description explains that projectId is optional and selects the project, and it enumerates the form-collected fields (title, description, due date, workflow status), so it meaningfully compensates for the undocumented 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 new task') plus the distinctive mechanism ('by asking the person ... in a native form'), which separates it from sibling item_create and create_project. An agent can identify this as the form-based creation path without opening 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?

Gives an explicit prerequisite and a named alternative: 'Requires a host supporting MRTR form elicitation; otherwise use item_create.' This is a direct when-to-use/when-not-to-use rule routed to a specific sibling.

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