Move selected test cases to a target TestRail section to reorganize and structure your test suites.
Moves specified test cases to a target section / 指定されたテストケースを対象のセクションに移動します
| Name | Required | Description | Default |
|---|---|---|---|
| caseIds | Yes | Array of TestRail Case IDs | |
| sectionId | Yes | Target TestRail Section ID |
Changes observed during successful MCP inspections.
v0.19.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. It only states the basic operation, omitting details like whether cases are removed from original section, permission requirements, or reversibility.
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 short and bilingual, efficiently conveying the core purpose without unnecessary 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?
With only two parameters fully described in schema, the description provides adequate basic info. However, lack of behavioral details and usage context leaves room for improvement.
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% with both parameters having descriptions. The description adds no extra meaning beyond the schema, so baseline 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 clearly states 'Moves specified test cases to a target section', identifying the action and objects. It distinguishes from sibling tools like moveSection (moves sections) and copyToSection (copies cases).
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 guidance on when to use this tool vs alternatives like copyToSection or updateCase. No prerequisites, when-not-to-use, or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.