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

With annotations already declaring destructiveHint=true and readOnlyHint=false, the description adds useful context: API-key scope is 'wiki:pages:write,' fields are resolved server-side as slugs, and the result is a moved page DTO. It does not explain secondary effects such as child-page movement, but it does not contradict the 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?

The main action is front-loaded and the optional-field semantics are packed into a compact sequence. The webUrl/citation sentence is useful but slightly tangential to the move operation, keeping it just below perfect conciseness.

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 rich schema, destructive annotations, and absence of an output schema, the description covers what an agent needs: move target behavior, slug resolution, cross-space moves, placement, return value, webUrl access semantics, and required API scope.

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 the baseline is 3. The description goes beyond the schema by clarifying that slugs are resolved server-side in the target space and by explaining the omit/null outcomes for targetSpaceKey, newParent, and afterPage.

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 states a specific verb and resource: 'Move a wiki page to a new parent and/or a new space.' This clearly distinguishes the operation from sibling tools such as wiki_update_page, wiki_create_page, and wiki_get_page.

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?

It explains the key usage scenarios for targetSpaceKey, newParent, and afterPage, including omit/null behavior for same-space moves, space-root moves, and first-position placement. It does not explicitly route the agent away from wiki_update_page, but the move-specific context is otherwise clear.

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