Move a section to a new parent or position within the TestRail test hierarchy by specifying its ID, target parent, and optional after ID.
Moves a section to a new position in the test hierarchy / テスト階層内の新しい位置にセクションを移動します
| Name | Required | Description | Default |
|---|---|---|---|
| afterId | No | ID of the section to position after | |
| parentId | Yes | Parent section ID (null for root) | |
| sectionId | Yes | 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 provided, and the description does not disclose any behavioral traits (e.g., effects on child sections, permissions required, reversibility). The description only states the basic action without side-effect awareness.
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 front-loaded with the English phrase. The Japanese duplicate is unnecessary but does not harm conciseness. No wasted sentences.
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?
No output schema and no annotations. The description lacks information about return values, error conditions, or behavioral constraints like whether the section must exist or the operation is reversible.
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% and all parameters have clear descriptions. The description does not add any extra meaning beyond the schema, so it meets the baseline for high-coverage scenarios.
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 a section to a new position in the test hierarchy', using a specific verb and resource. It distinguishes from siblings like 'moveToSection' (moves a case) and 'copyToSection' (copies a 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?
No guidance on when to use this tool versus alternatives such as 'addSection' or 'copyToSection'. No context about prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.