test

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

No annotations are provided, so the description carries the full behavioral burden. It discloses two useful behavioral traits: progress is streamed and there is no fixed client timeout. This goes beyond the schema and helps an agent understand the tool may be long-running. It does not address failure behavior or resource implications, but the core behavioral traits are present.

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 one sentence with no filler and front-loads the core action. The structure is slightly awkward—'suite Streams progress' reads like a missing sentence break—but it remains compact and information-dense.

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?

This is a high-complexity tool with 30 parameters, no annotations, and only partial schema coverage, yet the description provides only two behavioral facts: serial execution and streaming/no-timeout. Important context such as when to use this vs replay or batch, how sharding works, or what failure modes exist is missing. The output schema covers return shape, but invocation context is still under-specified.

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 30 parameters and only 60% schema description coverage, the description adds almost no parameter-level meaning. It only implies that 'paths' are the replay scripts via 'one or more replay scripts.' Many parameters such as retries, failFast, shardAll, shardSplit, timeoutMs, and recordVideo are left without description in either the schema or the tool description.

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 and resource: 'Run one or more replay scripts as a serial test suite.' This makes the core purpose clear. However, it does not distinguish this tool from siblings like 'replay' or 'batch', so an agent must infer the differentiator from 'serial test suite.'

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 phrase 'as a serial test suite' implies this tool is for running replay scripts in sequence, which gives some usage context. But there is no explicit guidance about when to choose this over 'replay' or 'batch', and no stated exclusions or alternatives.

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