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 states the tool 'adds' but fails to mention critical mutation details: that this operation creates test runs within the plan entry, may trigger notifications, or requires specific permissions. No mention of idempotency, side effects, or error conditions.

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?

Extremely concise single sentence that is front-loaded with the action. The bilingual format (English/Japanese) is efficient. Every word earns its place; there is no redundancy or filler content.

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 mutation tool with 10 parameters creating complex TestRail entities, the description is insufficient. No output schema is provided, yet the description doesn't explain return values or created artifacts. Lacks critical context about the plan entry lifecycle and its relationship to test runs.

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?

The input schema has 100% description coverage, so the description receives the baseline score of 3. The description itself adds no parameter-specific context (e.g., explaining the relationship between 'includeAll' and 'caseIds', or what 'runs' configurations should contain).

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 action ('Adds') and target resource ('test plan entry'), distinguishing it from sibling 'addPlan' by specifying 'entry' and 'existing test plan'. However, it assumes familiarity with TestRail domain concepts without explaining what a 'plan entry' represents (a test suite configuration within a plan).

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 tool versus alternatives like 'addRun' or 'addRunToPlanEntry'. No mention of prerequisites (e.g., requiring an existing plan ID) or when not to use it. The description only states what it does, not when to choose it.

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