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

Adds substantial context beyond the annotations (which only declare destructive/idempotent/openWorld/readOnly): the MRTR host requirement, that only accepted changes are saved, cancel semantics, and downstream effects ('may send configured notifications, webhooks and automation actions'). This is exactly the side-effect and environment disclosure the annotation set cannot carry.

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 tight sentences, front-loaded with the core action and mechanism, then constraints and side effects. Every clause carries distinct operational information with no padding.

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 single-param mutation tool with annotations but no output schema, the description covers identity, mechanism, host prerequisite, cancel behavior, fallback tool, and side effects. Nothing an agent needs to invoke it correctly 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% and the lone 'id' property is undocumented in the schema, but the description compensates by stating it accepts 'its UUID or task reference', clarifying the accepted identifier formats. It stops short of explaining the length/format constraints, so not a 5.

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+resource ('Edit an existing active task') plus the distinguishing mechanism ('Prefill a native form'), which separates it from create_task_form and plain item_update. An agent can tell exactly what this tool does 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 when-not and alternative: 'Requires a host supporting MRTR form elicitation; otherwise use item_update.' It also defines the cancel path ('Cancelling makes no change'), leaving nothing to inference about selection or abort behavior.

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