move_document

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

With no annotations, the description carries full burden. It describes the operation as a move but does not disclose behavioral traits such as whether the original document is removed from the source workspace, permissions required, or potential side effects. The return format is mentioned, providing some transparency.

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 well-structured with a summary, prerequisites, arguments list, and returns. It is concise and front-loaded, with no wasted sentences.

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 move operation, the description covers prerequisites, parameters, and return format. However, it lacks details on error conditions, reversibility, or constraints (e.g., workspace must be in the same organization), which could affect successful invocation.

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 description explains both parameters clearly: 'doc_id' as the ID of the document to move and 'target_workspace_id' as the ID of the destination workspace. Since the schema has 0% description coverage, this compensates fully.

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 ('Déplace un document vers un autre espace de travail') with a specific verb and resource, distinguishing it from sibling tools like create_document or delete_document.

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 explicit prerequisites (list_documents and list_workspaces) to obtain valid IDs, guiding the agent on preparation. However, it does not state when not to use this tool or mention alternatives, which would be helpful given the many sibling tools.

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