kiwi_delete_test_run

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

With no annotations, the description carries the burden of exposing risk; it does so by stating 'DESTRUCTIVE' and 'permanently delete,' clearly flagging irreversibility. It does not detail all consequences of a broad or empty filter, but the core danger is disclosed.

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?

Three short fragments cover action, resource, danger, and a parameter example with no filler. The warning is front-loaded, and every word 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?

The description is sufficient for a simple delete-by-id call, but it leaves the semantics of the filter open-ended; an agent could pass a broad dict and delete many runs without warning. There is also no return-value or verification note, which matters because the tool has no output schema and no annotations.

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 only shows an unconstrained 'query' object, so the description adds essential meaning by identifying it as an ORM filter dict and giving the concrete example {"id": 42}. More filter-operator detail would be useful, but the example compensates for the 0% schema coverage.

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 names a specific action ('permanently delete'), a specific resource ('test runs'), and a precise selection mechanism ('ORM filter dict'), so an agent can tell it apart from sibling delete tools such as kiwi_delete_test_case or kiwi_delete_entity.

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 and no mention of alternatives like kiwi_get_test_runs for verifying a filter before deletion. The only usage hint is the example filter {"id": 42}, which demonstrates syntax but not choice criteria.

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