go_to_slide

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

With no annotations, the description carries the full burden. It discloses the basic action (jumping to a slide) and the requirement of an active slideshow, but it does not mention error handling (e.g., out-of-range index), side effects, or return behavior. This is adequate but minimal for a simple navigation tool.

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 a single, front-loaded sentence of 9 words with no unnecessary information. Every word contributes to the purpose.

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 simple tool with one parameter and no output schema, the description provides the core functionality. However, it lacks details on return values or error conditions, which would help the agent handle edge cases. It is adequate 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?

The schema provides a full description for the single parameter (slideIndex: 1-based integer). The description adds no additional meaning beyond déjà-vu. Given 100% schema coverage, baseline score 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?

The description clearly states the verb 'jumps' and the resource 'specific slide' in the context of an 'active Keynote slideshow'. This distinguishes it from sibling tools like next_slide and previous_slide, which navigate sequentially, and start_slideshow, which initiates the show.

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 the tool is for jumping to a specific slide, but it does not explicitly state when to use it versus alternatives like next_slide or previous_slide. No exclusions or prerequisites beyond 'active slideshow' are provided, limiting guidance for the agent.

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