move_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that confirm must be true, that the item is removed from the source vault, that permissions may be required, or any side effects. 'Move' only weakly suggests a write operation.

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 short sentence with no filler, and the core action is front-loaded. It is concise, though it sacrifices important behavioral and usage detail.

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?

With eight parameters, no required fields, no annotations, and no output schema, this sparse description is insufficient for correct invocation. It leaves the agent to infer how to identify the item, how to specify source and destination via vault names versus share IDs, and what confirm and agentReason are for.

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 100%, so the baseline is 3 and the individual parameter descriptions already convey basic meaning. However, the tool description adds no guidance about parameter relationships, such as whether itemId and itemTitle are alternatives, or how fromVaultName/fromShareId should be combined.

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 states a specific action ('Move') on a resource ('an item') with a destination context ('from one vault to another'). This distinguishes it from item-level operations like update_item, trash_item, and delete_item, and from vault-level transfer_vault, though it does not explicitly contrast with those 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?

No guidance is provided about when to use this tool versus alternatives like transfer_vault or share_item. There is no mention of prerequisites, conditions, or exclusion criteria; the only usage context is implied by the name and the word 'move.'

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