Relocate a TestRail section under a new parent or at a specific position using its section ID.
Move a section to a new parent
| Name | Required | Description | Default |
|---|---|---|---|
| after_id | No | Section ID to insert after | |
| parent_id | No | New parent section ID (null for root) | |
| 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 present, so the description carries the full burden of disclosure. It only states the move operation and gives no detail about side effects, ordering behavior, handling of child sections, or whether the move is reversible. This is insufficient for a mutation tool.
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 concise sentence with no extraneous words and is front-loaded with the action. It is appropriately brief for the operation, though it is minimal to the point of omitting useful context.
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 three parameters, including an optional ordering parameter and a nullable parent_id, the description does not explain the semantics of the move beyond the schema. There is no output schema and no annotation, so the agent lacks important behavioral context such as what happens to the section's children or how after_id is interpreted.
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?
The input schema already describes all three parameters with 100% coverage. The description adds nothing about how after_id, parent_id, or section_id relate to the move operation beyond what the schema provides, so the baseline of 3 applies.
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 a specific verb ('Move'), a resource ('a section'), and the destination ('a new parent'), making the operation clear. It is distinct from siblings like move_cases_to_section and update_section, though it doesn't explicitly name them.
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 is given on when to choose this tool over alternatives such as update_section or move_cases_to_section. The usage is only implied by the operation described, with no explicit context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.