update-planner-task

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

Annotations indicate write and destructive operations. The description adds behavioral context: requires If-Match header (412 if missing), priority value mapping (0=Urgent, etc.), and ETag retrieval method. No contradictions with annotations.

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 sentences: one for purpose, one for critical tip. Front-loaded, no unnecessary words, every sentence adds value.

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 nested schema, it covers the most critical behavioral aspects (ETag, priority mapping). Does not describe output, but openWorldHint and no output schema imply variability. Adequate given complexity.

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 high (80%). The description enhances schema by explaining the If-Match header requirement and priority values, which are not fully detailed in the schema description. Adds meaningful context beyond 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?

The description clearly states 'Update the properties of plannerTask object' with a specific verb and resource, distinguishing it from sibling tools like create-planner-task, get-planner-task, and delete-planner-task.

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?

Provides a critical tip about the If-Match header and ETag requirement, including how to obtain it via get-planner-task with includeHeaders=true. While it doesn't explicitly contrast with alternatives, the sibling context makes usage clear.

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