Shortcuts List Shortcuts

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond the name: it does not explain what shortcuts are listed, what the optional folder_name does, or what the returned structure represents.

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 it is under-specified rather than concise. The single sentence is essentially a wrapper around the tool name and adds no informative value, so it does not earn its place.

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 is simple with one optional parameter and has an output schema, the description leaves the agent without any semantic grounding. An agent cannot determine what the tool lists, how folder_name affects behavior, or how this differs from several sibling tools.

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 one optional folder_name parameter with 0% description coverage, and the description does not compensate. Nothing explains whether folder_name filters results, matches a specific folder, or affects output in any way.

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 is a tautology: 'Delegated Apple domain tool shortcuts_list_shortcuts exposed through Apple-Tools-MCP' merely restates the tool name and platform without saying what the tool actually does. It does not state a verb, resource, or action beyond the name itself.

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 versus siblings like shortcuts_list_folders, shortcuts_view_shortcut, shortcuts_run_shortcut, or apple_list_shortcuts_for_capability. The description provides no context for selection or exclusions.

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