TestRail MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the output format (Gherkin) but fails to indicate safety profile (read-only vs destructive), error handling for invalid caseIds, or what the actual return value contains (file content string, path, etc.).

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?

Two sentences with zero fluff. The main action is front-loaded in the first sentence, and the requirement is stated immediately. The 'REQUIRED:' formatting is slightly abrupt but efficient.

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?

Given the single parameter and simple operation, the description covers the basics adequately. However, for an export tool lacking an output schema, it should mention what the tool returns (e.g., 'returns file content as string') to be complete.

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 caseId fully described as 'TestRail Case ID to export as .feature'. The description adds 'REQUIRED: caseId' which is redundant with the schema's required array. At 100% coverage, baseline 3 is appropriate as the description doesn't need to compensate.

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 the specific action (Exports), resource (BDD test case), and output format (.feature file in Gherkin format). It effectively distinguishes from sibling getCase by specifying the Gherkin export format versus standard case retrieval.

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?

While the format specificity (Gherkin/.feature) implicitly signals this is for BDD workflows, there is no explicit guidance on when to choose this over getCase or addBdd. The 'REQUIRED: caseId' emphasizes the parameter but doesn't provide usage context.

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