Files Open Path

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

Beyond annotations (openWorldHint=false, idempotentHint=false, destructiveHint=false), the description adds no behavioral context whatsoever. It does not disclose what opening means, whether a default app is launched, whether permissions are needed, or what side effects occur.

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 extremely short, but this is under-specification rather than useful conciseness. The single sentence mostly repeats the tool name and adds no operational value.

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?

With one parameter and an output schema the tool is simple, but even so the description leaves core semantics unstated: what file path it opens, in what app, and with what constraints. Sibling tools show a file-location context, but the description itself is incomplete.

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 explain the single required 'path' parameter, its format, absolute/relative requirement, or allowed file types. This is a clear gap since the schema provides only a bare string field.

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 name ('files_open_path') and says it is 'delegated' and 'exposed through Apple-Tools-MCP'; it does not state a verb-action like 'opens the file at the given path in the default application' nor distinguish it from apple_open_file_path/files_reveal_in_finder.

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 files_open_path versus any alternative such as files_reveal_in_finder, system_open_application, or apple_open_file_path. No prerequisites, exclusions, or selection criteria are given.

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