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

The annotations only say readOnly=false, destructive=true, openWorld=true; the description adds real behavioral context beyond that: the confirm=false preview vs. confirm=true execution split, that the shortcut runs its OWN actions under its own permissions rather than a sandboxed subset, that ambiguous names are refused rather than guessed, and that long/dialog-blocked shortcuts are bounded by a timeout instead of hanging.

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?

A single dense paragraph that front-loads the core purpose before the confirm flow, error behavior, and timeout. It is on the long side for three parameters, but nearly every sentence carries distinct operational information, so little is wasted.

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?

An output schema exists, so return formatting need not be restated. Given that, the description covers everything an agent needs: when the tool is appropriate, the two-step confirmation requirement, ambiguity handling, permission scope, and timeout behavior.

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 coverage is already 100%, so the baseline is 3, but the description adds semantics the schema does not: the two-step confirm ritual (preview names shortcut, identifier, and folder; confirm=true actually runs it), the refusal-and-retry behavior for ambiguous identifiers, and that input_text is passed via a temp file.

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?

States a specific verb and resource ('Runs one of the user's macOS Shortcuts by name or identifier') and immediately differentiates itself from the catalog by explaining it covers automation the rest of the tool set does not. An agent can distinguish this from shortcuts_list and shortcuts_view without opening any schema.

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?

Explains the context of use ('the way Mac users already automate HomeKit, Focus modes, and third-party app actions the catalog doesn't cover') and the prerequisite that the name comes from shortcuts_list. It does not explicitly name or rule out near alternatives such as recipe_run or run_terminal_command, so it stops short of full when/when-not routing.

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