testrail_get_results

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not say the operation is read-only, what the results contain, whether they are ordered, how pagination interacts with the limit parameter, or whether authentication/project access is required.

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?

A single, front-loaded sentence with no filler. It is efficient, though its brevity shades into under-specification rather than crispness.

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?

No output schema and no annotations mean the description must cover more ground, but it stops at restating the resource. It omits what a result record looks like, pagination behavior for limit, and how this differs from the case/run variants.

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 both test_id and limit are already documented in the schema. The description adds no format, range, or default detail beyond the schema, so the baseline 3 is correct here.

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?

States a clear verb+resource ('Get test results') and scopes it to 'a specific test', which implicitly separates it from the sibling tools testrail_get_results_for_case and testrail_get_results_for_run. However, it never makes that distinction explicit, so the agent must infer what a 'test' is versus a case or run.

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?

There is no when-to-use or when-not-to-use guidance. The phrase 'for a specific test' hints at the scoping, but the description never names the alternatives (get_results_for_case, get_results_for_run) or the condition that should route the agent to them, despite three near-identical siblings existing.

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