move_work_item_from_document

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

Discloses non-idempotency, HTTP 400 for free-floating items, and that item is preserved and re-attachable. Adds concrete error condition and checking procedure beyond annotations which already indicate destructive and non-idempotent.

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 concise sentences with no fluff, front-loaded purpose, and each sentence adds behavioral or usage 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?

Covers all critical aspects: action, preconditions, error handling, reversibility, and edge case (headings). With an output schema present, no need to explain return values. Complete for a 3-parameter tool.

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 100% with descriptions for all parameters. Description does not add additional meaning to parameters beyond what's in schema, so baseline 3 is appropriate.

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 'Detach a work item from its document' and emphasizes it's the ONLY detach path, distinguishing it from siblings like move_work_item_to_document. Uses specific verb and 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 explicit precondition: check via get_work_item, skip if already detached. Also mentions alternative re-attachment via move_work_item_to_document, giving clear when-to-use and when-not-to-use guidance.

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