TestRail MCP Server

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

With no annotations provided, the description fails to disclose critical behavioral traits: it claims to retrieve 'all' shared steps but doesn't explain the pagination behavior (limit/offset parameters), filtering capabilities, error handling for invalid project IDs, or response format. The word 'all' is misleading given the pagination parameters.

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 concise with two sentences (English/Japanese bilingual). No redundant words, front-loaded with the action. However, given the 9 parameters and lack of annotations, this brevity comes at the cost of completeness.

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 tool with 9 parameters (including pagination and filtering) and no output schema or annotations, the description is insufficient. It fails to mention that results are paginated, that extensive filtering is available, or what data structure is returned. The complexity demands more context.

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%, so the schema adequately documents all 9 parameters. The description mentions 'specified TestRail project' which loosely maps to projectId, but adds no additional context about the filtering parameters (createdAfter, updatedBy, etc.) or pagination syntax. Baseline 3 is appropriate since schema carries the load.

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 verb (Retrieves), resource (shared steps), and scope (specified TestRail project). It distinguishes from siblings like getCases/getRuns by specifying 'shared steps', though it could clarify what shared steps represent conceptually in TestRail.

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 provided on when to use this versus similar retrieval tools like getCases or getTests. No mention of prerequisites (e.g., valid project ID) or when not to use. The description is purely declarative.

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