tracecat_move_workflow_to_folder

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

Description discloses the ability to move to root via '/', and the verb 'move' implies relocation. No annotations exist, so the description adequately conveys behavior without contradictions.

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?

Single sentence with no superfluous words. Includes a concrete example for folder_path. Every word earns its place.

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 two-parameter move operation with no output schema, the description provides enough context. It covers the action and destination format. Could mention error cases or side effects but not strictly necessary.

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 has 100% coverage with descriptions identical to the tool description. The description adds no new information beyond the schema, so baseline score 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?

Description clearly states the action 'Move a workflow into a folder' and includes special case for root. It distinguishes from sibling tools like create_folder or update_folder.

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?

No explicit when-not or alternatives, but the tool is unique among siblings. The description implies use when moving a workflow to a specific folder or root, which is sufficient clarity for this simple operation.

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