kiwi_get_run_cases

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

With no annotations, the description carries the full burden. 'List' clearly indicates a read-only operation, and 'currently' signals that the returned set reflects the run's present membership. It does not mention pagination or ordering, but those are minor for such a simple retrieval.

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 a single focused sentence with no filler. The action and target are front-loaded, and every word contributes to understanding the tool's purpose.

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 one-parameter read-only endpoint, the description sufficiently conveys what the tool does. Since there is no output schema, the return value is inferable as test cases, and missing details like ordering or filtering are minor gaps.

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 schema has 0% description coverage and only provides the name 'run_id' with integer type. The description mentions 'a run' but does not explain how run_id is obtained, what it references, or any constraints. The parameter's meaning is mostly recoverable from the name, not from the description.

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 states a specific verb ('List') and a specific resource ('test cases currently in a run'). It clearly distinguishes this from siblings like kiwi_get_test_runs and kiwi_get_test_cases, which target different resources.

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 phrase 'currently in a run' implies this tool is for retrieving the case members of one specific run, but it does not explicitly say when to prefer this over alternatives or address exclusions. Usage context is recognizable but left to inference.

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