move_node

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

The description self-labels as MUTATING and mentions pre-checking the target category and apply_response_cap, but with no annotations provided, it fails to disclose important behaviors like side effects on connections, error conditions, or reversibility. The description carries the full burden but provides only minimal insight.

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 concise, with two short sentences. It front-loads the core action. The inclusion of 'add-node-parameter-vex-tools' is somewhat cryptic but doesn't detract significantly from readability.

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 no annotations, no output schema, and no parameter descriptions, the description is the only source of context. It fails to mention return values, error handling, or the purpose of ctx. The operation's simplicity aside, too much essential context is missing.

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 0%, so the description must compensate. It explains dest_parent as the target parent and implies src_path is the node to move, but ctx is not mentioned at all. No formats or examples are given, leaving substantial gaps for the parameters.

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 node to a dest_parent, which is a specific verb+resource. This distinguishes it from sibling tools like copy_node or delete_node. The purpose is immediately understandable.

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?

No guidance is provided on when to use this tool versus alternatives such as copy_node or connect_nodes. The description mentions the underlying Houdini function but gives no context about scenarios or prerequisites, leaving the agent without decision criteria.

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