Files Recent Files

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

The description adds no behavioral context beyond the annotations. It does not disclose whether the tool is read-only, whether it requires special permissions, how results are ordered, what counts as 'recent', or what the output contains. The agent is left entirely to the name and the output schema.

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. It contains only boilerplate framing that could apply to any delegated Apple tool, so the brevity does not serve the agent's decision-making.

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 has an output schema and a single optional parameter, the description is too hollow to support reliable selection or invocation. It does not explain what recent files means, how limit affects behavior, or how this tool differs from the many file-related siblings.

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 for this gap. The single parameter 'limit' is left completely unexplained: no meaning, units, bounds, or behavior when omitted. The description adds no value beyond the schema's 'Limit' title and default value.

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 in a wrapper phrase ('Delegated Apple domain tool ... exposed through Apple-Tools-MCP') without stating what the tool does. The only real signal is the name itself, which implies listing recent files but is never explicitly confirmed.

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 use this tool versus closely related siblings such as files_list_directory, files_search_files, files_list_recent_locations, or files_get_file_info. No usage context, exclusions, or alternatives are provided.

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