outlook_delete_task_attachment

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's only real claim ('Remove') merely restates them. It adds no context on irreversibility, whether the attachment can be recovered, or any permission/ownership requirement for a destructive operation.

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?

One short sentence with the action and target front-loaded and no filler. It is efficient, though the brevity is achieved by omission rather than by disciplined editing.

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 destructive mutation with three undocumented parameters and no output schema, the description supplies almost nothing an agent needs to call it safely or correctly. The list_id ambiguity alone makes it insufficient.

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 bears full responsibility, yet it names no parameters at all. In particular the optional 'list_id' is left completely unexplained, so an agent cannot tell when it must be supplied versus omitted.

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 ('Remove') and resource ('an attachment from a To Do task'), which clearly separates it from siblings like outlook_upload_task_attachment, outlook_download_task_attachment and outlook_remove_draft_attachment. It does not explicitly name a sibling to contrast with, so it lands just short of a 5.

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 when-to-use or when-not-to-use guidance and no mention of prerequisites such as needing the parent task or list context. The agent must infer entirely from the verb that this is the deletion counterpart to upload/list.

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