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

Annotations already declare destructiveHint=true and idempotentHint=false, so the agent knows this can overwrite state and is not repeat-safe. The description adds that this is scoped to a single scope item and that 'move' implies replacing an existing deadline, but says nothing about permissions, whether a prior deadline is lost, or what happens on an unknown scope item.

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 tight sentences with the action front-loaded and the format detail second; nothing is redundant or padded.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. However, for a destructive mutation on a required scopeItemId/engagementId pair with no parameter descriptions, the definition is thin on preconditions and side effects.

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 0%, so the description must compensate and it only does so partially: it explains dueOn's calendar-day YYYY-MM-DD semantics, which the schema already conveys via pattern. engagementId and scopeItemId are left entirely undocumented in both the schema and the description, which is a real gap for a 3-required-parameter tool.

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 states a specific verb pair ('set or move') and resource ('the deadline') scoped to 'one scope item', which separates it from siblings like save_rate and save_scope_item by resource. It is clear and actionable, though it does not explicitly name a sibling or state a boundary against them.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the approval-related siblings (approve_scope, approve_change_order) that might gate deadline changes. 'Set or move' implies the intent, but the agent is left to infer all context.

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