move_link

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

With no annotations, the description must fully disclose behavior. It indicates movement but does not mention whether the operation is reversible, requires specific permissions, or has side effects. This is insufficient for a mutation tool.

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 precise sentences, no wasted words. Front-loaded with the core action, followed by essential ID retrieval and special case instructions. Excellent efficiency.

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 simplicity of a move operation, the description covers the main usage pattern: how to get IDs and how to handle root. The schema covers omitted parameter behavior. Lacks output details, but no output schema exists, so not required.

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 coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema, primarily restating the null behavior for targetFolderId. No new parameter-level insights are provided.

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 clearly states 'Move an existing link to a different space or folder', using a specific verb and resource. It distinguishes well from sibling tools like add_link, open_link, and list_links by focusing on relocation.

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?

Provides guidance on obtaining link IDs ('Get link IDs from list_links or search') and handling the root case ('pass targetFolderId as null to move to root'). Lacks explicit when-not-to-use or alternative selections, but the action is clear.

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