wiki_move_document

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

With no annotations, the description must fully disclose behavioral traits. It only states the operation (move/reorder) but does not mention permissions required, side effects on document structure, or whether the action is reversible. The presence of an output schema does not compensate for missing behavioral context.

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 a single sentence that efficiently captures the tool's action and two use cases. It is front-loaded and avoids redundancy, though a slightly expanded structure could improve clarity.

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 the tool's complexity (move/reorder) and lack of annotations, the description should provide more context on parameter semantics and behavioral consequences. The presence of an output schema does not fully compensate for the missing guidance on when and how to use the 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 description coverage is 0%, yet the description provides no explanation of parameters. The meaning of 'parent_id' (default 0) and 'position' (default 0) is not clarified, leaving the agent to infer without guidance.

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 clearly states the tool moves a document to a new parent or adjusts its position among siblings, distinguishing it from sibling tools like wiki_create_document or wiki_update_document. It uses a specific verb ('move') and resource ('document'), and the two use cases are well-defined.

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 guidance is provided on when to use this tool versus alternatives like wiki_update_document, which might also change parent. There is no mention of prerequisites, exclusions, or context where moving is inappropriate.

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