replay_scenario

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

The description discloses that execution may fail with an error and specifies the return format, but with no annotations provided, it does not fully disclose potential side effects or safety profile (e.g., whether it modifies state).

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 with a clear front-loaded summary and structured Args/Returns sections, each sentence earning its place without redundancy.

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 simple single parameter and lack of output schema, the description covers the main purpose, parameter usage with examples, and expected return value, but could mention prerequisites or result structure in more detail.

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 significant meaning to the single parameter 'path' by providing an example and clarifying it can be a name or file path, which goes well beyond the schema's bare 'string' type.

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 'Load a previously saved scenario spec and execute it,' using specific verbs and resource, and the tool name 'replay_scenario' implies replaying a saved one, distinguishing it from siblings like 'run_scenario' and 'save_scenario'.

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 context for when to use the tool (to load and execute a saved scenario) and implies usage via the parameter description, but does not explicitly exclude alternatives or provide when-not guidance.

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