patch_folder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool moves a folder, but does not disclose important details such as whether the move is recursive (subfolders and files moved), any restrictions on the target parent (e.g., cannot be a descendant), permissions required, or what happens to folder contents. 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?

The description is a single sentence, which is concise. However, it could be slightly more detailed without losing conciseness (e.g., adding 'Use to change the parent folder of a folder'). It is front-loaded and gets the main point across immediately.

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 the tool (2 params, likely straightforward behavior), the description should at least clarify whether the move is recursive and any constraints on the target parent. With no annotations and minimal description, the tool definition is not complete enough for an AI agent to use correctly without additional context.

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 0% parameter description coverage, so the description must compensate. However, it only mentions moving 'to a different parent,' hinting at the 'parent_folder_id' parameter, but does not explain the 'folder_id' parameter or the meaning of an empty string default for 'parent_folder_id' (e.g., move to root?). The description adds minimal semantic value beyond what can be inferred from parameter names.

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 tool moves a folder to a different parent. It uses a specific verb ('Move') and identifies the resource ('folder') and the change ('different parent'). This distinguishes it from sibling tools like 'update_folder' (which would modify other properties) and 'create_folder' (which creates new folders).

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 implies usage for moving folders, but it does not explicitly state when to use this tool versus alternatives. For example, it does not mention that 'update_folder' should be used for renaming or other modifications, nor does it provide any prerequisites or conditions for moving (e.g., permission requirements).

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