move_work_item_from_document

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

Adds concrete behavior beyond annotations: non-idempotency leads to HTTP 400, headings become free-floating with empty space_id/outline_number, and module clearing. No contradiction with annotations.

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?

Concise 4-sentence description front-loads primary action and includes key behavioral notes. Slightly dense but well-structured.

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 detach action, error behavior, heading special case, and preservation. Output schema exists (not shown) but behavioral disclosure is sufficient for a moderate-complexity 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 descriptive parameter descriptions. The description adds no extra semantic value for parameters, meeting the baseline expectation.

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?

Clearly states it detaches a work item from its document, returning to free-floating state. Explicitly identifies as inverse of move_work_item_to_document, distinguishing it from siblings.

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?

Specifies it is the only detach path and provides constraints (e.g., non-idempotent, heading behavior). Mentions inverse sibling but could improve by explicitly stating when NOT to use (e.g., work item already free-floating).

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