show_slide

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

No annotations are provided, so the description carries the burden. It does disclose the key side effect — the user's live view is moved — which is the important non-obvious behavior. It omits prerequisites (does a presentation need to be open/connected?) and error behavior when navigation is impossible.

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, purpose first, then the workflow guidance. No filler and nothing redundant with the schema.

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 2-parameter navigation tool with no output schema and no annotations, the description covers purpose, effect on the user, and when to call it. Missing only edge-case behavior around live-session availability.

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 slideIndex documented as zero-based and presentationId documented as optional when only one presentation is connected. The description adds nothing about parameters, so the baseline 3 applies.

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 and resource ('bring a slide into view in the live presentation') and clarifies the effect with a parenthetical ('navigates the user to that slide'). This clearly separates it from read-only siblings like inspect_slide or screenshot_slide without naming them.

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?

Gives explicit when-to-use guidance: call BEFORE editing so the user can watch changes, and for slide-by-slide walkthroughs. It lacks any when-not or failure condition (e.g., what to do if no live session exists), which keeps it from a 5.

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