delete-planner-task-message

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

Goes beyond the annotations (destructiveHint=true) by detailing behavior: no request body, optional If-Match for conditional deletion, 204 response, and clear limitations (beta, delegated work/school accounts, global cloud only). This gives the agent a solid understanding of constraints and effects.

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?

Compact and well-structured: opens with the purpose, then a useful tip with key operational details, and closes with limitations. Every sentence adds information; no fluff or repetition.

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 delete tool with two required path parameters and a well-documented schema, the description covers purpose, behavior, return code, and constraints. With no output schema, it doesn't need to explain return values. An agent has everything needed to invoke it correctly.

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 has 100% coverage, so the baseline is 3. The description adds value by explaining that If-Match is optional and for conditional deletion, which the schema label 'ETag' doesn't fully convey. However, it doesn't elaborate on the required path parameters beyond what the schema already states.

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 the exact operation 'Delete a plannerTaskChatMessage object' and adds a clarifying tip that it deletes a message from a Planner task's chat. Clearly distinguishes from sibling tools like create and list by using the delete verb and target resource.

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 context on deletion and conditional deletion with If-Match, and notes account/cloud restrictions. It doesn't explicitly name alternatives or say 'use this when you want to remove a message', but the purpose is unambiguous so an agent can infer the right time to use it.

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