Shortcuts List Folders

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

The annotations already indicate readOnlyHint=true and idempotentHint=true, but the description adds no behavioral context beyond the bare name. It does not mention return shape, scope of folders, sorting, permissions, or any other runtime behavior, and the 'Delegated' phrasing is architectural boilerplate rather than useful behavior disclosure.

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 the only sentence mostly repeats the tool name and adds generic 'Delegated ... exposed through Apple-Tools-MCP' filler. It is not meaningfully concise because it packs no useful information.

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?

The tool is simple to invoke: no parameters, read-only annotations, and an output schema exist. However, the description still fails to explain what Shortcuts folders are or what the result represents, leaving the agent to infer the entire purpose from the tool name.

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 has zero parameters and an empty input schema, so there are no parameter semantics for the description to clarify. This matches the baseline of 4 for tools with no parameters.

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 only restates the tool's name as 'shortcuts_list_folders' and wraps it in 'Delegated Apple domain tool ... exposed through Apple-Tools-MCP' boilerplate. It never directly states what the tool does, such as listing folders in the Shortcuts app, so an agent must rely on the name alone.

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?

No guidance is given about when to use this tool instead of related tools such as shortcuts_list_shortcuts, shortcuts_view_shortcut, apple_list_shortcuts_for_capability, or notes_list_folders. The description provides no usage context, prerequisites, or exclusions.

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