apple_keynote_open

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

Annotations declare readOnlyHint=false, openWorldHint=true, and idempotentHint=false, but the description adds genuinely new behavioral context beyond them: the app is launched and a window or import dialogs may appear. That side-effect disclosure is exactly what an agent needs to anticipate UI disruption from this non-idempotent operation.

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?

Two tight sentences, front-loaded with the action and followed by the side-effect warning. No wasted words.

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 single-parameter open tool with no output schema, the definition covers what the tool does and the notable side effects. Only the missing path-format detail and when-to-use context keep it from being fully complete.

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?

One required parameter with 0% schema description coverage, so the schema alone does not explain 'path'. The description partially compensates by implying it is a path to a local Keynote document, but adds no format, extension, or relative-vs-absolute guidance.

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+resource ('Open a local Keynote document') with a 'local' scope qualifier that separates it from remote/web document operations. It is easily distinguished from sibling mutations like apple_keynote_create or apple_keynote_close, though it never names a sibling explicitly.

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?

No guidance on when to open vs. create, save, or export, and no prerequisites or preconditions (e.g., document must exist locally). Usage is only implied by the verb.

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