Move one or more media items to a different folder in your library. Use echosaw_list_media to find mediaIds and echosaw_list_folders to find target folder paths.
| Name | Required | Description | Default |
|---|---|---|---|
| mediaIds | Yes | Array of mediaId strings to move | |
| targetFolderPath | Yes | Destination folder path (e.g., "/Marketing/Q1 2026") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false and destructiveHint=false, so it's clear this is a non-destructive write operation. The description adds little beyond stating it moves items, and does not disclose potential side effects (e.g., overwriting, folder existence requirements).
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 and front-loaded with the action. Both sentences earn their place: the first states the purpose, the second provides crucial input-finding guidance. No filler or redundancy.
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's simplicity and rich annotations, the description is mostly complete. It covers what, how, and where to find the parameters. It could mention whether the target folder must pre-exist, but the instruction to use list_folders implies it. No output schema exists, so missing return details are acceptable.
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 coverage is 100%, so each parameter is well-defined. The description adds value by explaining how to obtain valid values (using list_media for mediaIds and list_folders for targetFolderPath), which goes beyond the schema's basic definitions.
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 ('Move one or more media items to a different folder') with a specific verb and resource. It distinguishes itself from sibling tools (list, create, delete, rename folders) by focusing on moving media items.
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 practical guidance on how to find the required inputs by directing users to echosaw_list_media and echosaw_list_folders. It implies when to use this tool (when moving media), but does not explicitly contrast with alternatives like 'when not to use'.
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 targets a distinct action and resource: analysis jobs (submit, check, get results, download), folder management (create, delete, list, rename), media operations (list, move, search, set visibility), and account info (organization, profile). There is no overlap or ambiguity between tools.
All tools follow the consistent pattern `echosaw_<verb>_<noun>`, using clear verbs like analyze, check, create, delete, get, list, move, rename, search, and set. The naming style is uniform and predictable across the entire set.
With 14 tools, the server covers a well-scoped platform for media analysis and library management. Each tool serves a clear purpose without feeling bloated or sparse, fitting comfortably within the ideal range.
The server covers the full analysis workflow, folder organization, media searching, and account retrieval. Minor gaps exist such as lack of media deletion or job cancellation, but core workflows are well supported and no critical dead ends are apparent.
