start_slideshow

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action and optional starting slide, but does not mention side effects (e.g., whether it changes presentation state), failure conditions (e.g., no presentation open), or whether it is idempotent. This lack of detail leaves the agent in the dark about critical 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 description is extremely concise: a single sentence with no unnecessary words. It front-loads the key action and includes the optional parameter. Every word 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?

Given the tool's low complexity (one optional parameter, no output schema), the description is minimally adequate but has gaps. It does not mention that the presentation must be frontmost or that starting a slideshow might interrupt an existing one. For a simple action, it is functional but not thorough.

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 coverage is 100% with the 'fromSlide' parameter well-described in the schema (type, description, exclusive minimum). The description merely echoes 'Optionally start from a specific slide', adding no new semantic value beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states it starts the slideshow of the frontmost Keynote presentation, optionally from a specific slide. The verb 'starts' and resource 'slideshow of frontmost Keynote presentation' are specific and well-distinguished from siblings like stop_slideshow, next_slide, etc.

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 implies usage when one wants to start a slideshow, but does not provide explicit guidance on when to use versus alternatives (e.g., go_to_slide, next_slide). There is no mention of when not to use or prerequisites, such as requiring a presentation to be open.

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