apple_shortcuts_list_folders

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

The 'Read-only:' prefix merely restates readOnlyHint=true from the annotations, so it adds no value beyond structured data. Nothing is said about what the folders represent, ordering, or how the results are consumed, and no annotation already covers those points.

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 short sentence with the purpose front-loaded and no padding. The only waste is the 'Read-only:' prefix that duplicates the annotation, but the definition stays tight.

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 zero-param read tool this covers the essentials, but with no output schema the description could say what folders are returned (names, ids) and whether they feed other Shortcuts tools. That return-shape gap keeps it at minimum-viable.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no input is required to enumerate folders.

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: 'list Shortcuts folders.' An agent can separate it from the sibling apple_shortcuts_list (which lists shortcuts rather than folders), though the description never names that distinction explicitly.

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 on when to call this versus apple_shortcuts_list or other sibling listing tools, and no preconditions are stated. The usage context is left entirely to inference from the tool name.

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