TestRail MCP Server

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

No annotations provided, yet description fails to disclose read-only safety, idempotency, return format (array of strings vs objects), or whether results are project-scoped or global.

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 efficient sentence with Japanese translation. No redundant words, though bilingual format slightly splits semantic focus for monolingual agents.

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 a parameterless lookup tool, but lacks return value description needed given the absence of an output schema. Should indicate whether it returns metadata objects or simple identifiers.

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?

Zero parameters present; baseline score applies. Description correctly implies no filtering is possible ('all available'), matching the empty schema.

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?

Clear verb 'Retrieves' and resource 'test case types in TestRail' with bilingual coverage. Distinguishes from sibling 'getCases' by specifying 'types', though it doesn't explain what constitutes a case type (e.g., Functional vs Regression) to fully differentiate from 'getCaseFields'.

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 explicit guidance on when to use this versus creating cases directly, or whether this is a prerequisite for 'addCase'. No mention of caching or frequency of use.

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