Move specified test cases to a different section in TestRail by providing case IDs and target section ID. Organize test suites by relocating cases to the appropriate section.
Move cases to another section
| Name | Required | Description | Default |
|---|---|---|---|
| case_ids | Yes | Array of case IDs to move | |
| suite_id | No | Suite ID | |
| section_id | Yes | Section ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'Move cases to another section' only states the basic action; it does not mention side effects like removal from the source section, possible data loss, permission requirements, or irreversibility.
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, direct sentence with no filler. It front-loads the core operation and wastes no words.
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?
This is a mutating tool with no annotations and no output schema, yet the description is only a bare statement of intent. It does not explain what happens to the original location, whether suite_id is needed, or how this differs from copy_cases_to_section in practical use.
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%, so the schema documents all parameters. The description adds only minimal clarification that section_id is the destination section ('another section'), but it does not explain the role of the optional suite_id or otherwise enrich the parameter semantics.
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 states the exact operation: moving cases to a section. It clearly differentiates from the sibling tool 'copy_cases_to_section' by using 'move' rather than 'copy', and from 'move_section' by specifying 'cases' rather than 'section'.
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?
There is no guidance on when to use this tool versus alternatives like copy_cases_to_section or move_section. The description implies the operation but does not state conditions, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.