Shortcuts View Shortcut

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

Annotations declare readOnlyHint and idempotentHint, so the safety profile is already covered. However, the description itself contributes no behavioral information at all, such as whether the tool returns shortcut details, requires specific permissions, or has any special limitations.

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 short, but brevity here reflects under-specification rather than conciseness. The single sentence earns no value because it merely wraps the tool name in a generic 'delegated Apple domain tool' statement.

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?

Even though the tool has one parameter and an output schema, the description provides no functional context. An agent cannot determine what the tool does, what input to supply, or how it differs from neighboring shortcut tools, so the definition is functionally incomplete.

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 schema has 0% description coverage, so the description must clarify what shortcut_name_or_identifier means and what formats are accepted. The description does not mention the parameter or provide any examples, leaving the agent to guess whether a display name, UUID, or other identifier is expected.

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 'Delegated Apple domain tool shortcuts_view_shortcut exposed through Apple-Tools-MCP' merely restates the tool name and adds generic framework context. It does not state that this tool views a shortcut or what viewing entails, so an agent cannot determine the tool's actual function.

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?

There is no guidance about when to use this tool instead of siblings like shortcuts_list_shortcuts, shortcuts_run_shortcut, or apple_route_or_run_shortcut. The description provides no selection criteria or context of use.

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