replay

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the basic action without revealing whether the operation is destructive, requires authentication, or has rate limits. The agent has no insight into side effects or constraints.

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 extremely concise (one sentence), but it sacrifices informativeness for brevity. It is not front-loaded with essential details; instead, it provides only the bare minimum.

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 high parameter count (22) and lack of output schema or annotations, the description is severely incomplete. It does not explain return values, error conditions, or the overall workflow. The agent cannot properly understand or invoke this tool based on the description alone.

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 description adds no meaning beyond the input schema. Although schema description coverage is 77%, the description does not highlight which parameters are critical (e.g., 'path,' 'session') or clarify their roles. The agent must rely solely on the schema, which for some parameters (like 'path') lacks a 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 'Replay a recorded session,' which is a verb+resource but lacks specificity. It does not clarify what type of session (e.g., UI interaction, test execution) or how the session was recorded. While it distinguishes from the sibling 'record,' it does not differentiate from other session-related tools like 'session' or 'batch.'

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives (e.g., 'record' to create a session first, or 'test' to run tests). There is no mention of prerequisites, context, or exclusions.

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