Run Playtest Suite

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

The description discloses key behavioral traits beyond the readOnlyHint=false annotation: it enters Play Mode, requires no confirmation, and describes how stop_after exits Play Mode. It also explains the output format. This provides useful operational context that annotations do not cover.

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 well-structured with an overview, parameter breakdown, and output summary. It is sufficiently detailed but not overly verbose; each sentence contributes to understanding the tool's behavior or parameters.

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 7 parameters and no output schema, the description covers most aspects: the parameter relationships, the output shape, and the action. It lacks an explicit usage context compared to alternatives, but the information provided is sufficient for an agent to invoke the tool correctly. The missing timeout_per_test description is the main gap.

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?

With 0% schema description coverage, the description compensates well by explaining the format and accepted values for pattern, suite_path, and the boolean flags (stop_on_fail, stop_after, auto_play, restart_between). However, the timeout_per_test parameter is not described at all, leaving a gap for that parameter.

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 states the tool runs multiple .playtest files sequentially and returns a compact matrix. It explicitly mentions entering Play Mode, which is a specific action. It distinguishes from siblings like 'run_playtest' by indicating batch execution of multiple files.

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 clear parameter usage guidance, including the constraint that exactly one of pattern or suite_path must be provided, and explains the effect of each flag. However, it does not explicitly state when to choose this tool over alternatives like 'run_playtest' or other test runners; the usage context is implied rather than stated.

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