delete-planner-task-message

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

Beyond annotations (destructiveHint=true), the description adds: BETA status, conditional deletion behavior, response status, and authentication/scope requirements. This is substantial additional context that helps the agent understand the tool's behavior.

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?

The description is well-structured: starts with purpose, then a tip with key details in bullet points. Every sentence adds information without redundancy. It's concise yet comprehensive.

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?

The description covers deletion action, usage details, response, and constraints. It could include more about error handling or idempotency, but for a delete tool with no output schema, it is fairly complete.

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 provides 100% description coverage for all 5 parameters. The description adds value by explaining 'If-Match is optional if you want conditional deletion', which clarifies the parameter's intent beyond the schema's 'ETag' label.

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 'Delete a plannerTaskChatMessage object' and explains it deletes a message from a Planner task's chat, making the action and resource very clear. The name is specific enough to distinguish it from sibling delete tools like 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?

The description provides usage tips: no request body, optional If-Match for conditional deletion, returns 204. It also specifies account and region constraints (delegated work/school only, global cloud). It lacks explicit comparison to alternatives but the context is informative.

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