Run macro script

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

The description adds rich behavioral context beyond annotations, such as dispatching entries through tool handlers, dryRun avoiding invocation, stopOnError halting on first failure, and the warning about redacted args failing at the tool boundary. This complements the annotations without contradicting them.

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 two concise sentences, front-loaded with the core action and followed by parameter details and a warning. Every sentence adds value 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 complexity of a tool that dispatches to other tool handlers, the description covers the essential behavior, parameters, and a security caveat. No output schema exists, but for a side-effect-driven replay tool, the description adequately guides usage, though it does not mention return values or the overall expected outcome.

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 0% schema coverage, the description carries full responsibility for parameter semantics. It explains each parameter's purpose: dryRun for planning, stopOnError for failure handling, argsOverrides for shallow-merging replacements, and allowRawPython for opting into raw-Python entries, plus the macroPath is implicitly the file to replay.

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: replay a MacroRecord JSON file by dispatching entries through in-process tool handlers. This specific verb (replay) and resource (MacroRecord JSON file) distinguishes it from siblings like macro_recorder, which records rather than replays.

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 detailed parameter usage guidance (dryRun, stopOnError, argsOverrides, allowRawPython) but does not explicitly state when to use this tool versus alternatives or when not to use it. The usage context is implied by the purpose, but no exclusions or sibling comparisons are provided.

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