List Open Presentations

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds value by specifying the return payload: each presentation's name, full path, save state, slide count, and active status. This goes beyond the annotation and helps the agent understand what to expect from the call.

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 two sentences, with the core purpose front-loaded. The return format is summarized in a compact bullet-style without wasted words. Every sentence earns its place, and the structure makes the key information immediately visible.

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 no-parameter, read-only listing tool, the description is complete. It explains what the tool returns, and the absence of an output schema is compensated by the explicit list of return fields. There is no missing information an agent would need to call this tool correctly.

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 zero parameters, and the schema is an empty object. The description correctly omits parameter details since there are none. With no parameters to document, a baseline of 4 is appropriate—the description does not need to add anything further.

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 states exactly what the tool does: 'List all presentations currently open in PowerPoint.' The verb is specific ('List'), the resource is clear ('open presentations'), and the scope ('all') distinguishes it from operations on a single presentation. The sibling tool get_presentation_info appears to target one presentation, so this is clearly a bulk enumeration tool.

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 clearly implies the tool is for enumerating open presentations, but it does not explicitly say when to use it versus alternatives like get_presentation_info or mention any exclusions. The context makes the primary use case obvious, but the lack of explicit guidance on alternatives leaves a minor gap.

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