Delete a TestRail section by its ID. Optionally use soft delete for preview-only removal, keeping the section available for recovery.
Deletes a section / セクションを削除します
| Name | Required | Description | Default |
|---|---|---|---|
| soft | No | True for soft delete (preview only) | |
| 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 are provided, so the description must disclose behavioral traits. It only says 'deletes a section' without mentioning the soft delete parameter or whether deletion is permanent, reversible, or has side effects.
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 extremely short and to the point, with no unnecessary words. The bilingual addition is minor and does not detract from conciseness.
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 is provided, and the description does not explain return values, error handling, or the effect of the 'soft' parameter. For a destructive operation, this is insufficient.
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 described in the input schema. The description adds no additional meaning beyond what the schema provides, meeting the baseline.
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 'Deletes a section', specifying the verb and resource. Among sibling tools, deleteSection is the only one for deleting sections, so it is well-differentiated.
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 like moveToSection or archive. No prerequisites or conditions are mentioned, such as requiring the section to be empty.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.