move-wiki-page

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

Goes beyond the annotations by disclosing the key side effect that child pages move together by default and can be excluded via withChildren=false — an important cascading behavior for a destructiveHint=true operation. It stops short of stating permissions requirements, reversibility/undo, or what the response contains, but the annotation already flags the destructive profile.

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?

Front-loads the verb and the three modes, then lists examples compactly. Minor waste: the parenthetical Korean translation duplicates the English title and adds no information for an agent already reading the English description.

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 6-parameter mutation tool with no output schema, the description covers all three move modes, the default child-move behavior, and worked examples for each. That is enough for an agent to select and invoke it correctly; missing return format is not required since none is documented.

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%, so baseline is 3, and the description adds real value by showing parameter combinations (reparent, move-only, move-to-top with beforePageId '0') rather than just restating field meanings. The examples make the interplay between targetParentPageId and beforePageId concrete.

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 and resource ('Move a wiki page') and enumerates the three distinct move semantics: reparenting, cross-wiki relocation (targetWikiId), and sibling reordering (beforePageId). This clearly separates it from update-wiki-page and move-drive-file in the sibling list.

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?

Explains the three supported move modes and gives concrete invocation examples, which makes the when-to-use case clear. It does not explicitly contrast with update-wiki-page (rename/content edits) or warn about when not to use it, so routing to alternatives is left implicit.

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