move_wiki_node

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects (e.g., impact on children nodes), required permissions, or error states. The '[Official API]' tag adds slight credibility but does not compensate for the lack of behavioral details.

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 sentences with no redundant information. The first sentence states the purpose, the second provides parameter guidance. Each sentence is essential and front-loaded.

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 tool with 4 parameters and no output schema, the description explains the core action and parameter constraints but omits return value, error handling, and confirmation of success. It is adequate but incomplete for a non-trivial mutation 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%, but the description adds value by clarifying the optional parameters: 'target_space_id (optional; same-space move if omitted)' and the constraint that at least one of target_parent_token/target_space_id must be provided. This goes beyond schema descriptions.

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 verb 'move' and the resource 'Wiki node', specifying scope: to a different parent within the same space or to a different space. This distinguishes it from sibling tools like copy_wiki_node, delete_wiki_node, and create_wiki_node.

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?

The description includes explicit guidance on parameter usage: 'Pass at least one of target_parent_token / target_space_id.' It implies the tool is for moving nodes but does not explicitly mention when not to use it or provide alternatives. However, the required constraint is clear.

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