move_to_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The parenthetical 'removes from current collections' is a critical, non-obvious side effect that prevents the agent from mistaking 'move' for 'add to collection'. It does not mention failure modes or collection-existence requirements, but the core mutation behavior is transparent.

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, front-loaded sentence that states the action and immediately adds the key caveat about removing from current collections. Every word earns its place and there is no filler.

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 tool with an output schema, the description conveys the essential operation and side effect. It is missing guidance on valid identifier formats and whether the target collection must be pre-created, which may matter for correct invocation. The presence of list_collections as a sibling helps, but the description does not point the agent to it.

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 schema provides no parameter descriptions (0% coverage), so the description must compensate. It does clarify that 'object' is the thing being moved and 'collection' is the destination, but it does not specify whether these are names, IDs, or paths, nor whether the collection must already exist. This is adequate but not fully compensating for the schema gap.

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 pairing: 'Move an object to a collection', and the parenthetical 'removes from current collections' makes the operation unambiguous. It is clearly distinct from sibling tools like create_collection, delete_collection, or set_collection_visibility.

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 gives clear context: use this tool when an object should be relocated into a target collection, removing it from its current collections. It does not explicitly name alternatives, but no sibling tool performs this same move operation, so the exclusion is not needed.

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