wiki_move_docs_to_wiki

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'move' but does not specify whether the original document is removed, whether the operation is reversible, required permissions, or potential side effects on links or references. This lack of detail leaves significant behavioral ambiguity.

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, direct sentence with no unnecessary words. It efficiently communicates the core purpose without restating schema information or adding filler. This is exemplary 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 tool's moderate complexity (4 parameters, no annotations, no output schema), the description is too minimal. It fails to explain the overall workflow, such as how to obtain the target space_id or what happens to the original document. The schema covers parameter syntax but not contextual details like prerequisites or side effects, leaving the tool description incomplete for an agent to use reliably.

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 100%, so all parameters are already explained in the schema. The description adds no additional meaning to the parameters, making the baseline score of 3 appropriate. The description does not help clarify the relationship between parameters or any special formatting.

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 specific action (move documents) with a source (cloud space) and target (knowledge base). This distinguishes it from sibling tools like wiki_move_node, which likely operate within the wiki, by specifying the cross-domain move context.

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 provides no guidance on when to use this tool versus alternatives such as wiki_move_node. It does not mention prerequisites, exclusions, or conditions under which this tool is preferred. The purpose implies a usage context, but no explicit guidance is given.

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