Move Document

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

Annotations only state readOnlyHint=false and destructiveHint=false. The description adds critical behavior—the document is removed from the source vault—which is not directly implied by the annotations. This clarifies the mutation effect, though it omits details about permissions or failure scenarios.

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 exceptionally concise: two short sentences that front-load the action and resource, with a second sentence adding the critical removal detail. No fluff or 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?

For a simple tool with two parameters and an output schema, the description covers the core behavior adequately. However, it does not address edge cases like moving to the same vault, permission requirements, or how to handle non-existent documents, leaving minor gaps.

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 no descriptions for the two parameters, and the tool description does not elaborate on doc_id or target_vault beyond their names. The phrase 'different vault' hints at target_vault's role, but no format, identifier type, or usage details are provided, leaving the agent to infer.

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 the action ('Move'), the resource ('a document'), and the destination ('a different vault'). It also explicitly notes that it removes the document from the source vault, which distinguishes it from vault_copy_doc and other sibling tools.

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 removal clause implies a key difference from copying, but the description does not explicitly name alternatives or provide exclusion criteria. It lacks guidance such as 'use instead of copy when you want to remove the source' or 'do not use for archiving.'

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