outliner-object_move

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does not clarify what 'move' does to the object's prior collection memberships, whether multiple source collections are allowed, what happens if the target collection does not exist, or any mutation side effects.

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 sentence with no filler. It front-loads the action and includes the key constraint in a compact, readable way.

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 simple two-parameter mutation tool, the description gives the core operation but is incomplete overall. With no annotations, no output schema, and zero parameter documentation, the agent is left without enough context to know identifier formats, prerequisites, or behavioral consequences of moving an object.

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%, and the description does not compensate. It only restates 'object' and 'target collection' without explaining the expected format, identifier type, or constraints for these 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 uses a specific verb and resource: 'Move an object to exactly one target collection.' It clearly states both the action and its destination, and the 'exactly one' constraint helps distinguish it from sibling tools like outliner-object_link and outliner-object_unlink.

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 about when to use this tool instead of alternatives such as outliner-object_link, outliner-object_unlink, or outliner-parent_set. The phrase 'exactly one target collection' implies a constraint, but the description does not explain the intended context or exclusions.

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