move_documents

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

With no annotations provided, the description must convey behavioral traits. It only says 'move', which implies removing the source, but this is not explicit. It does not disclose side effects, reversibility, or authorization needs, which is a significant gap 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?

The description is concise with one sentence for purpose and one for a parameter. It is front-loaded and efficient, but could include more context without becoming verbose.

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 tool has no annotations and two required parameters, the description is insufficient. It does not cover return values (though output schema exists), safety, or how it interacts with sibling tools like 'copy_documents' or 'delete_document'. The minimal info leaves the agent uncertain.

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 'document_ids_csv' as a comma-separated list of document IDs, which adds meaning beyond the schema. However, 'folder_id' is not explained, and since schema coverage is 0%, the description only partially compensates.

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 documents to a folder' with a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'copy_documents', which could cause confusion about whether the move is destructive.

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 no guidance on when to use this tool versus alternatives like 'copy_documents', nor does it mention prerequisites such as required permissions or whether the documents and folder must belong to the same project.

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