test

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

No annotations are present, so the description must carry behavioral disclosure. It only states that replay scripts are run serially; it does not mention execution side effects, failure semantics, output behavior, or any special requirements. This leaves most behavior undisclosed.

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 sentence and free of filler, making it easy to parse. It is compact but this brevity comes at the cost of behavioral and parameter guidance.

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?

With 38 parameters, no annotations, and a complex execution model, one sentence is far too little to make the tool safely invocable. It lacks guidance on serial behavior details, platform/device selection, retries, fail-fast, or output levels; the output schema compensates only for return-value documentation.

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 already documents 68% of parameters, and the description adds value by clarifying that 'paths' are replay scripts. But it offers no semantics for the other 37 parameters, many of which (retries, failFast, shardAll) are not described in the 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 uses a specific verb ('Run') and resource ('one or more replay scripts') and adds the mode 'serial test suite', which distinguishes it in intent from sibling tools like replay or batch. However, it doesn't explicitly contrast itself with those siblings, so not a full 5.

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 given about when to choose this tool over related siblings such as replay or batch; the only hint is the phrase 'serial test suite,' which implies a batch-testing use but does not elaborate on alternatives or conditions.

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