mac_recipe_run

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

No annotations are present, so the description carries the transparency burden. It explicitly notes that execution stops on the first failed step (no partial rollback) and that steps inherit the recipe's app context. These are useful behavioral disclosures beyond the raw action.

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 front-loaded with the core purpose, then gives three concise examples, then lists two limitations. It is compact and well-structured without unnecessary fluff.

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?

While it covers purpose, usage, and limitations, there is no mention of what the tool returns or what happens after execution. Since there is no output schema, the agent is left guessing about the result format.

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 input schema already describes all parameters (100% coverage), so the baseline is 3. The description adds value with concrete examples showing how to pass params as an object and how dryRun previews steps, which helps clarify parameter intent.

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 opens with 'Run a saved recipe by name with parameter values,' a specific verb-and-resource statement. It clearly differentiates from sibling tools like mac_recipe_save and mac_recipe_search by focusing on execution.

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 concrete examples (toggle-dark-mode, open-url-with-params, dryRun) but does not explicitly discuss when to prefer this tool over siblings like mac_run. The usage context is implied rather than stated as a rule.

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