TestRail MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only implies mutation via the verb 'moves'. It fails to disclose whether child sections move with the parent, if the operation is atomic, or what happens if invalid parent/section IDs are provided.

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?

Single sentence structure with bilingual text (English/Japanese) is appropriately front-loaded. While efficient, the Japanese duplication may be unnecessary for agents operating in English-only contexts, slightly reducing the score from perfect.

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?

Adequate for basic hierarchy manipulation given the 100% schema coverage, but lacks critical context for a tree-move operation: no mention of circular reference prevention, cascading effects on children, or return value expectations (no output schema exists).

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%, establishing a baseline of 3. The description mentions 'new position' which loosely maps to the afterId/parentId parameters, but adds no additional semantic clarity about how parentId and afterId interact to determine final placement.

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?

Clearly states the tool moves a section to a new position using specific verb (Moves) and resource (section). However, it fails to distinguish from the similarly-named sibling tool 'moveToSection', which could cause selection confusion.

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?

Provides no guidance on when to use this tool versus alternatives like 'updateSection' or 'moveToSection'. Does not mention prerequisites such as requiring valid section IDs or potential conflicts with existing hierarchies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.