Files List Directory

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

Annotations declare readOnlyHint and idempotentHint, which already cover the safety profile. The description adds no behavioral context beyond that—it does not clarify what listing a directory entails, whether it is recursive, what paths it accepts, or any side effects. There is no contradiction with annotations, but also no added transparency.

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 this is under-specification rather than effective conciseness. It contains no functional information and earns none of its sentence, failing to front-load any useful meaning.

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?

Despite having output schema and read-only/idempotent annotations, the core behavior is entirely missing. An agent cannot know what this tool returns, what paths are valid, or how it differs from the many other files_* tools in the sibling list. The description is inadequate for correct invocation.

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%, and the description does not compensate. The single 'path' parameter is left undefined beyond its type and title; the description gives no indication whether it must be a directory path, a file path, an absolute path, or a relative path.

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 merely restates the tool name ('files_list_directory') and says it is a 'Delegated Apple domain tool' exposed through Apple-Tools-MCP. It never states that the tool lists the contents of a directory or what resource it operates on, making it essentially a tautology.

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 files_search_files, files_get_file_info, or files_list_recent_locations. The description provides no context, prerequisites, or exclusions, leaving the agent without any basis for selection.

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