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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the stateful nature of the call is covered. The description adds useful context by scoping the action to a "live presentation" (a running session rather than a stored deck), but it says nothing about behavior at the final slide or when no presentation is active.

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 twelve-word sentence with the action and target front-loaded and zero filler. There is no structural waste to trim.

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?

With no parameters and no output schema, the surface area an agent must understand is small. Still, the description omits failure conditions (no active presentation, already at last slide) that would matter for a stateful navigation call, leaving the definition merely adequate rather than 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter-level meaning is missing because none exists.

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 ("Advance") and resource ("the live presentation") with an explicit increment ("by one slide"). It implicitly distinguishes itself from goto_slide and previous_slide, though it never names those siblings to make the contrast unambiguous.

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 word "Advances" implies a forward-only navigation step, so usage is inferable, but the description gives no explicit when-to-use guidance and never mentions the obvious alternatives (previous_slide, goto_slide) or preconditions such as requiring an active live session.

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