System Open Application

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

The description provides no behavioral information beyond the annotations. It does not disclose that this launches an application, whether it is safe, what side effects it has, or whether it requires permissions. With no coverage from the description, the agent cannot infer operational behavior.

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 one-sentence description is short but under-specified; it is not concisely informative. It restates the tool name and adds a generic 'exposed through Apple-Tools-MCP' wrapper, which does not earn 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?

Even though an output schema exists, the description is completely inadequate for a two-parameter tool. There is no explanation of what the tool does, when to invoke it, or how the optional parameters relate. An agent could not confidently select or call this tool based on the provided context.

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 adds no meaning to bundle_id or application. Both parameters are optional and nullable, but the description does not explain how to choose between them, whether one supersedes the other, or what values are expected.

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 essentially a tautology: it only says the tool is 'Delegated Apple domain tool system_open_application exposed through Apple-Tools-MCP.' It never states that the tool opens an application, what inputs it accepts, or what effect it has. It does not distinguish this from the sibling apple_open_application.

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 alternatives. Sibling tools like apple_open_application, files_open_path, and system_list_running_apps exist, but the description gives no conditions, exclusions, or selection criteria.

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