apple_shortcuts_list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false; the description's 'Read-only' prefix largely restates them. It does add the useful scoping fact that results can be constrained to a folder, but discloses nothing about volume, ordering, or permission needs. With annotation coverage present, a 3 fits.

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 tight sentence with the scope qualifier front-loaded after the verb. Nothing is padded or redundant.

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?

For a one-optional-parameter read tool with annotations covering the safety profile and no output schema, the description is adequate but thin. It leaves the relationship to apple_shortcuts_list_folders and the exact folder-argument behavior unstated.

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 description coverage is 0% for the single 'folder' parameter, so the description must carry meaning. It does indicate the parameter is optional and filters by folder, but adds no detail on name matching, case sensitivity, or invalid-folder behavior.

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 ('list') and resource ('installed Shortcuts') with scope ('optionally in one folder'), so the core operation is unambiguous. It does not explicitly distinguish itself from the sibling apple_shortcuts_list_folders, which an agent might reasonably confuse when looking for folder data.

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 statement of when to use this tool, when not to, or which alternative applies. The 'optionally in one folder' clause is parameter scoping rather than usage guidance, so the agent gets no routing help against siblings like apple_shortcuts_list_folders.

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