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

With no annotations present, the description carries the full burden of behavioral disclosure, and it does so richly. It explains server-side pagination, a 20-page/5000-test cap, the meaning of returned T-id and C-id, status ID mapping, and the capReached caveat, which is critical for avoiding false negatives.

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 well-structured and front-loaded with the primary purpose. Each sentence delivers distinct value: pagination handling, return fields, filtering, and limits. No filler or redundant information—every clause earns its place.

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?

Despite having no output schema, the description fully explains what the tool returns (fields, IDs, status), how pagination works, and the critical capReached caveat. The two parameters are adequately covered, and the description is sufficient for an agent to invoke the tool correctly, even in complex triage scenarios.

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% for both parameters, so the baseline is 3. The description adds value beyond the schema by explaining the statusIds filter with concrete examples, clarifying the meaning of runId (R-number) implicitly, and teaching the relationship between test instances and case IDs. This is helpful but not exhaustive, hence a 4.

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 tool lists every test inside a TestRail run, with a specific verb ('List'), resource ('tests inside a TestRail run'), and distinctive scope (all pages, server-side pagination). It distinguishes itself from sibling tools that list cases or runs by explicitly mentioning test instances and run context.

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?

The description provides clear context for when to use this tool: when you need tests within a run, and it suggests filtering by statusIds for triaging failed tests. It also hints at the relationship to testrail_get_case. However, it does not explicitly name alternative tools or state when not to use it (e.g., versus testrail_list_cases).

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