getRun

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

With no annotations provided, the description must fully disclose behavior. It only states 'retrieves details' without mentioning that it is a read-only operation, any missing behavior like error handling, or what constitutes 'details'. This falls short for a mutation-free tool.

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, consisting of one bilingual sentence that communicates the core action. It is front-loaded and efficient, though the bilingual repetition could be seen as redundant but not detrimental.

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?

The description is minimal but adequate for a simple retrieval tool with only one parameter. However, it lacks details on what 'details' include (e.g., fields returned, error handling) and does not leverage the opportunity to differentiate from similar sibling tools. Given no output schema, more context would be helpful.

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 already describes the single parameter 'runId' with a clear description ('TestRail Run ID'), achieving 100% coverage. The description does not add further meaning beyond the schema, so a baseline of 3 is appropriate.

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' and the resource 'details of a specific test run by ID', providing a specific action and resource. It distinguishes from sibling tools like 'getRuns' (plural) and 'getTests' by focusing on a single run by ID.

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 is provided on when to use this tool versus alternatives, such as when to use 'getRun' versus 'getRuns' or 'getTests'. There is no mention of prerequisites, exclusions, or common use cases.

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