transfer_collection_items

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Transfer items between collections' implies a mutation operation but doesn't specify whether this requires special permissions, whether it's reversible, what happens to source items in 'move' mode, whether there are rate limits, or what the response format looks like. For a tool with 5 parameters including complex nested objects, this is inadequate 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 maximally concise at just 4 words: 'Transfer items between collections'. It's front-loaded with the core action and contains zero wasted words. For a tool name that already indicates 'transfer_collection_items', this efficiently reinforces the purpose 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?

Given the complexity (5 parameters including nested objects, no annotations, no output schema), the description is insufficiently complete. A mutation tool that transfers items between collections needs more context about permissions, side effects, response format, and error conditions. The minimal description doesn't compensate for the lack of structured behavioral metadata.

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 has 100% description coverage, so all parameters are documented in the structured schema. The description adds no additional parameter semantics beyond the basic concept of 'transfer items between collections'. It doesn't explain relationships between parameters (e.g., how 'target' and 'location' interact, what 'model' fields represent, or the implications of 'copy' vs 'move' modes). Baseline 3 is appropriate when schema does the heavy lifting.

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 'Transfer items between collections' clearly states the verb (transfer) and resource (items between collections), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling operations like 'move_collection_items' or 'copy_collection_items' that might exist in other contexts, though none are listed among the provided siblings.

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. With siblings like 'fork_collection', 'merge_collection_fork', 'sync_collection_with_schema', and various create/update/delete operations for collection components, there's no indication of when transfer is appropriate versus those other operations. No prerequisites, constraints, or comparison context is mentioned.

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