run_tests

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

With no annotations, the description bears the full burden of explaining behavior. It discloses timeout termination and return structure, which is useful, but it does not mention potential side effects of running tests, resource usage, or whether the sandbox fully isolates the process.

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 compact, front-loaded with the core purpose, and uses a clear Args/Returns structure. Every sentence contributes useful information without redundancy or filler.

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 tool with two optional parameters, the description covers behavior, parameters, and return format. The main gap is the lack of guidance about when to use this instead of get_test_output, but the presence of an output schema and clear parameter docs make it mostly complete.

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 coverage is 0%, so the description must explain the parameters itself. It fully does: test_target is described as a relative file or node with a concrete example, and timeout_seconds includes its default and meaning. This adds substantial meaning beyond the raw schema.

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 ('Execute'), a well-defined resource ('automated pytest tests'), and a context ('repository sandbox'). This clearly distinguishes it from siblings like get_test_output, which retrieves results rather than running 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?

The description tells what the tool does but gives no explicit guidance on when to choose it over alternatives such as get_test_output or apply_patch. There is no mention of when not to use it, prerequisites, or how it relates to sibling tools.

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