Move Item To Organization

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

Annotations indicate non-destructive mutation. The description adds that the result is a summary with redaction rules, but does not disclose whether the original item is removed from personal vault or other side effects. Behavioral context is adequate but not comprehensive.

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?

Two sentences, front-loaded with the core action, no redundant wording. Every sentence adds essential information about the operation and behavior.

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 absence of an output schema, the description mentions the return value. It covers required vs optional parameters. Lacks details on prerequisites (e.g., item must not already belong to an organization). Comprehensive for a move operation with moderate complexity.

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 provides descriptions for all 3 parameters (100% coverage). The description adds value by clarifying that collectionIds are organization collections, not personal folders, which is meaningful beyond the schema's structural description.

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 the specific verb 'move' and clearly identifies the resource as 'an existing vault item' to a 'required organizationId'. It distinguishes from siblings like delete or create by focusing on moving between contexts.

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 implicitly states when to use (move item to organization), but does not provide explicit guidance on when not to use or mention alternative tools for similar operations (e.g., keychain_edit_org_collection for modifying collections).

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