open_presentation

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

No annotations are provided, so the description carries the full burden. It discloses the state change ('make it the current presentation') but says nothing about what happens to the previously open presentation and any unsaved changes, nor about error behavior for invalid paths or non-.pptx files.

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 short, front-loaded sentences; the primary purpose comes first and the Args block is minimal. Nothing is padded, though the Args block adds nearly no information.

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 single-parameter tool this is close to adequate, and there is no output schema to explain. However, the absence of annotations means the description should cover state side effects and failure modes, which it largely omits.

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 description coverage is 0%, so the description must compensate, but its 'path' text merely restates the parameter name. It gives no guidance on absolute vs. relative paths, expected extension, or behavior on a wrong-format path.

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 ('Open an existing .pptx file') and adds the state effect ('make it the current presentation'). The word 'existing' implicitly separates it from create_presentation, though no sibling is named.

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?

Usage is only implied: open a file that already exists rather than creating one. There is no explicit when-to-use, no mention of what to do if the file is missing or already open, and no routing to create_presentation for new decks.

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