focus_previous_presentation

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Focus the previous presentation' implies a state-changing operation, but it doesn't specify whether this requires permissions, what happens to the currently focused presentation, whether it's reversible, or if there are side effects. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits undisclosed.

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, efficient sentence with zero wasted words. It's appropriately sized for a zero-parameter tool and front-loads the core action. Every word earns its place, making it highly concise and well-structured for quick comprehension.

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 complexity implied by sibling tools and the lack of annotations or output schema, the description is incomplete. It doesn't explain what 'focus' entails operationally, what 'previous' means in context, or what the expected outcome is. For a tool that likely changes system state among many alternatives, more context is needed to guide proper use.

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 has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics because none exist, which is appropriate. A baseline of 4 is applied since the schema fully covers the parameter landscape (none), and the description doesn't need to compensate.

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 'Focus the previous presentation' is essentially a tautology that restates the tool name with minimal elaboration. It specifies the action (focus) and resource (previous presentation), but doesn't clarify what 'focus' means operationally or how it differs from similar tools like 'focus_presentation' or 'focus_active_presentation' in the sibling list. The purpose is stated but lacks meaningful differentiation from alternatives.

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 is provided on when to use this tool versus alternatives. With many sibling tools like 'focus_presentation', 'focus_active_presentation', and 'focus_next_presentation', the description offers no context about prerequisites, timing, or what constitutes a 'previous' presentation. The agent must infer usage from the name alone, which is insufficient for informed tool selection.

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