Move an existing assignment into a folder (or out of any folder).
| Name | Required | Description | Default |
|---|---|---|---|
| folder | Yes | Destination folder (id, name or full path), or 'none' to remove it from its folder | |
| assignment_id | Yes | Assignment id (from list_assignments) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description clearly conveys that this mutates the assignment-folder relationship rather than creating or deleting anything, which complements the readOnlyHint=false, idempotentHint=true, and destructiveHint=false annotations. It also adds the non-obvious behavior of being able to remove the assignment from its folder entirely. No contradictions with annotations.
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 focused sentence with no redundant words. The primary operation is front-loaded, and the parenthetical adds an important edge case without bloating the text.
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 low-complexity tool with two fully documented parameters, idempotency/non-destructiveness annotations, and no output schema, the description plus schema covers the essential usage. It could mention what the call returns upon success, but that is a minor gap for a simple move operation.
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 the individual parameter descriptions already explain that folder accepts an id, name, full path, or 'none', and that assignment_id comes from list_assignments. The tool description adds no additional parameter nuance, so the baseline of 3 is appropriate.
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 ('Move') with a clear resource ('existing assignment') and target ('folder'), and explicitly covers the reverse operation ('or out of any folder'). This makes it easy to distinguish from related siblings like move_folders, create_assignment, or update_assignment.
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 intended use is implied by the action itself: use it to place an assignment in a folder or remove it from one. However, there is no explicit guidance about when to prefer this over update_assignment, move_folders, or other folder-related tools, and no when-not-to-use conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct target resource/action, and the descriptions are unusually explicit about differences (e.g., 'Distinct from the watchlist', 'Separate list from list_tags'). A few pairs are still easy to confuse without careful reading: delete_folder vs delete_folders differ only by singular/plural, and the three download-URL tools (get_post_download_url, get_asset_download_url, get_my_account_post_download_url) plus the category/tag families require attention to pick correctly.
The snake_case verb_noun pattern is followed consistently throughout (list_*, get_*, create_*, update_*, delete_*, set_*, tag_*). Minor deviations: archive_folder and archive_my_accounts also perform restore despite their names, delete_folder/delete_folders split one operation by cardinality, and tag_posts/tag_my_account use a different verb style than the set_* family for metadata mutations.
At 56 tools, this far exceeds the 25+ threshold for 'too many,' even though the server spans multiple subdomains (watchlist, analysis, assignments, folders, my accounts, assets, Drive, categories/tags). Obvious consolidation candidates exist — delete_folder/delete_folders, the three download-URL getters, and the parallel list_my_account_* listers — and the sheer surface is heavy for an agent to navigate.
Core workflows are thoroughly covered with no dead ends: watchlist → analyze → assign → folder → track → approve has full lifecycle support, including reversible archive vs permanent delete choices. Minor gaps exist but are work-aroundable: no create/update for my accounts or models (app-side OAuth/admin only), no way to delete a viral post or a post note, and asset upload only happens in the app.
