generate_and_run_tests

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

With no annotations, the description carries the full burden of disclosing behavior. It does reveal the testing frameworks and that execution instructions are included, but it says nothing about side effects such as writing files, modifying the project, or actually running builds/tests. The gap between the tool name ('run_tests') and description ('execution instructions') is also not clarified.

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, dense sentence that front-loads the main action and key technologies. There is no fluff. It could be slightly more structured to separate generation from execution, but it is efficient and readable.

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 tool supports five test types, has four parameters, no formal annotations, and no output schema, yet the description does not explain what 'execution instructions' means, whether tests are actually run, or what the generated output looks like. A multi-mode tool with this complexity needs more contextual detail to be safely invoked.

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 schema already documents all four parameters and the testType enum. The description adds no extra parameter-level meaning. This is acceptable under the baseline rule, but it also does not explain how parameters like methodsToTest or targetCode are used together.

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 identifies the tool as generating Kotlin tests and names specific frameworks (MockK, Turbine, createComposeRule), making the purpose specific. It does not explicitly differentiate itself from sibling tools like generate_compose_screenshot_tests, but the core purpose is not vague. However, the tool name says 'generate_and_run_tests' while the description only mentions 'execution instructions,' creating some ambiguity about whether it actually executes tests.

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 about when to use this tool versus alternatives. There is no mention of when generate_and_run_tests is preferred over generate_compose_screenshot_tests or generate_kotlin_mock_factory. The context for choosing among the testType enum values is also absent.

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