outlook_remove_draft_attachment

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

No annotations exist; description only says 'remove', implying a modifying operation, but fails to disclose what happens on failure, whether it returns anything, or if irreversible. Lacks behavioral depth.

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?

Extremely concise (one sentence), no wasted words. However, could be slightly expanded to include critical usage hints without being verbose.

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?

Given no output schema, no annotations, and only 2 params without descriptions, the description fails to provide important context like return value, error handling, or how to get attachment IDs. Incomplete for effective tool use.

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 0% description coverage; description mentions 'by attachment ID' but does not explain what attachment_id means or how to obtain it, nor what draft_id refers to. Adds little beyond parameter names.

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?

Description clearly states it removes a single attachment from a draft by ID, distinguishing it from sibling tools like outlook_attach_to_draft (adds) and outlook_delete_draft (deletes entire draft).

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?

No mention of when to use this tool vs alternatives, no prerequisites (e.g., draft must exist, attachment must be present), and no context about expected results or errors.

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