test

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention any side effects, required permissions, error conditions, or the nature of script execution (e.g., synchronous vs. asynchronous). The single sentence 'Run one or more replay scripts' is insufficient.

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 concise (one sentence), but it is too terse for a tool with 34 parameters. It fails to front-load important details or structure information hierarchically. While brevity is valued, this sacrifices clarity and completeness.

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?

Given the tool's complexity (34 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain what happens after running scripts, how results are returned, or how to interpret success/failure. The description is inadequate for an agent to use this tool reliably.

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 62%, which is moderate but not high. The description adds no value beyond the parameter names in the schema. Critical parameters like 'paths', 'env', 'failFast', and 'timeoutMs' are not explained in the tool description, leaving the agent to rely solely on the schema's sparse descriptions.

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's function: 'Run one or more replay scripts.' It uses a specific verb ('run') and resource ('replay scripts'), making the purpose clear. However, it does not differentiate itself from the sibling tool 'replay', which may cause confusion.

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 no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or scenarios where this tool is preferred over siblings like 'replay', 'batch', or 'record'.

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