TestRail MCP Server

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

No annotations provided, so description carries full burden. Only states creation occurs; omits return value format, error conditions (e.g., invalid projectId), idempotency, side effects, or authentication requirements. Fails to disclose that includeAll and caseIds are typically mutually exclusive.

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 bilingual sentence is appropriately compact and front-loaded. Japanese translation adds length but serves internationalization purpose without reducing clarity. No redundant or wasted text.

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?

For a 10-parameter creation tool with no output schema or annotations, description is insufficient. Missing critical workflow constraints (includeAll vs caseIds relationship), return value documentation, and distinction between standalone runs vs plan entries.

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 has 100% description coverage, establishing baseline 3. Description adds no supplemental parameter guidance (e.g., syntax for refs field, mutual exclusivity of includeAll/caseIds, or milestone assignment logic), but schema adequately documents individual fields.

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?

States specific verb (Creates) + resource (test run) + context (TestRail project). Clearly distinguishes from siblings like addPlan, addCase, addSuite by specifying 'test run' as the target entity.

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 vs. addPlan/addRunToPlanEntry, nor prerequisites like requiring suiteId for multi-suite projects. No mention of alternative tools or workflow context.

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