wiki_delete_node

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

With no annotations, the description fully discloses the behavior: it does not delete the node but moves it out, and explains the two-step workflow due to API limitations. It also explains the underlying file remains and can be deleted later, which is important 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 two short sentences, front-loaded with the action and outcome, plus essential information about the two-step deletion. Every sentence earns its place without redundancy.

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 moderate-complexity move operation with no annotations and no output schema, the description covers the purpose, effect, limitation, and follow-up action. It could mention potential side effects on child nodes or permission requirements, but these are not critical for the primary use case, so it is nearly complete.

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?

The input schema already has 100% coverage with descriptions for both space_id and node_token, including a clarification that node_token is not obj_token/document_id. The tool description adds no extra parameter meaning, so it meets the baseline but does not exceed it.

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 wiki node out of the wiki to the cloud space root directory, which is a specific, distinct action. It also differentiates from sibling tools like wiki_move_node by specifying 'out of the wiki' and from drive_delete_file by noting it is a prerequisite step.

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 explicitly explains when to use this tool (when wanting to delete a wiki node, since Feishu has no public API for direct wiki deletion) and provides the next step (use drive_delete_file). This gives clear usage context and points to an alternative, satisfying the dimension.

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