List execution statuses

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

The readOnlyHint annotation already informs the agent this is a safe read operation. The description adds the list of possible execution statuses (IDLE, PASSED, FAILED, BLOCKED) which gives useful domain context, though it does not describe pagination, filtering behavior, or return format beyond the schema.

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 short line, which is concise in word count, but it is more of a code snippet than a structured explanation. It lacks a clear front-loaded purpose statement and reads as under-specified rather than efficiently distilled.

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?

There is no output schema, so the description should convey what the tool returns; it only lists possible statuses without explaining the response structure or the meaning of 'filter'. The tool is simple, but the description leaves ambiguity about whether this returns all statuses or filters by the query parameter.

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 the parameters (limit and query) are fully documented in the schema. The description does not add anything beyond the status value list, which is not directly tied to the query parameter semantics, so a baseline 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 title clearly states 'List execution statuses', but the description relies on a technical reference 'TestExecutionStatus.filter: IDLE, PASSED, FAILED, BLOCKED…' rather than an explicit verb. It implies the tool surfaces these status values but doesn't plainly describe the action, and it doesn't distinguish it from sibling list tools like kiwi_list_case_statuses beyond the resource named in the title.

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 no context for when to use this tool versus alternatives, such as case statuses or execution lists. There is no mention of prerequisites, typical use cases, or exclusions, leaving the agent to infer from the name alone.

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