Files List Recent Locations

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

Annotations already declare readOnlyHint and idempotentHint, so the operation's safety profile is known. However, the description itself contributes no behavioral context—no mention of scope, limitations, or what 'recent locations' means.

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 brevity is not conciseness when the only sentence is a restatement of the tool name. It contains no useful information that earns its place.

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 and has an output schema, but the description still fails to explain what the tool returns, what a 'recent location' is, or how 'limit' affects behavior. The provided context is insufficient for reliable selection and 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 one parameter 'limit' is left entirely unexplained. Since the description must compensate for the missing schema documentation and does not, the agent gets no semantic help for the parameter.

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 is a tautology: it repeats the tool name and states it is an 'Apple domain tool' without defining what the tool actually does. There is no verb, no resource, and no distinction from siblings like files_recent_files.

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?

The description provides no guidance on when to use this tool versus alternatives such as files_recent_files, files_list_directory, or files_search_files. It does not mislead, but it also gives the agent nothing to select on.

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