open_application

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

No annotations are present, so the description bears the full burden; it does disclose the meaningful launch-or-focus semantics (idempotent behavior). But it says nothing about behavior on an unknown app name, whether it blocks until the app is ready, permission requirements (e.g., accessibility/automation), or failure modes.

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?

A single tight sentence with the action front-loaded and examples appended; every element earns its place with no filler.

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?

For a one-parameter, no-output-schema tool this is close to minimally sufficient to invoke correctly. It still leaves the agent guessing about error behavior and name-matching rules, which matters for a launch action whose failure mode is user-visible.

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?

The single param has 0% schema description coverage, so the description must compensate; the inline examples ('Safari', 'Slack') usefully clarify that the parameter is a human-readable app name. It does not address case sensitivity, exact-name matching, or what identifier forms are accepted.

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?

States a specific verb pair (launch/focus) plus the resource (application) and the argument format ('by name'). It is clearly distinguishable from siblings like list_applications and inspect_app by virtue of being an action, though it never explicitly contrasts itself with app-specific activators such as chrome_activate or ax_activate.

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 phrase 'launch or focus' implicitly signals this is safe to call whether or not the app is already running, which is useful usage context. However, it names no alternatives and gives no when-not guidance, so an agent facing chrome_activate / chrome_focus / ax_focus siblings gets no routing help.

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