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

Annotations already indicate this is not read-only and not destructive, but the description adds no behavioral context beyond that. It does not state whether existing folder assignments are replaced or added to, whether the operation is reversible, or whether moving has side effects on reports, assets, or permissions. 'One or more folders' is a minor addition but does not meaningfully disclose behavior.

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 with no filler or redundant phrasing. It front-loads the action and keeps the key detail—'one or more folders'—prominent. It is appropriately sized for a simple two-parameter tool.

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?

The tool is simple, has full schema coverage for parameters, and includes annotations and an output schema, so the description does not need to explain return values. However, the core semantics of 'move' are ambiguous: it does not specify whether the client is removed from all current folders and placed only in the listed ones, or whether the listed folders are appended. For a move operation, this is a meaningful gap.

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 description coverage is 100%, and both parameters already have clear descriptions including source hints ('from list_clients' and 'from list_folders'). The tool description itself adds no parameter information, so the baseline 3 is appropriate. The description does not clarify whether the folders array is a complete replacement list or an additive set.

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 uses a specific verb-resource pair: 'Move a client to one or more folders.' It clearly distinguishes this from sibling tools like move_widget or update_client, and the phrase 'one or more folders' adds precise scope. It is not a tautology despite resembling the title, because it expands the title with the multi-folder capability.

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 gives no guidance on when to use this tool versus alternatives such as update_client, create_folder, or move_widget. There is no mention of prerequisites, use cases, or exclusions. The only implied context is that the tool is for reassigning clients to folders.

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