read_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 clearly states the tool reads a presentation and returns slide content, implying a non-mutating operation. However, it does not disclose output granularity, extraction limitations (e.g., text vs. images), or error behavior for invalid paths.

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 minimal and front-loaded: one sentence for the tool's purpose, followed by a clearly formatted Args section. Every part earns its place with no filler.

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, read-only tool with no output schema, the description covers the essential information: what it reads, what it returns, and what the argument means. Minor gaps remain around the exact format of the returned slide content and handling of invalid files, but these are not critical for basic invocation.

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?

With 0% schema description coverage, the description compensates by explaining the path parameter as 'Path to the .pptx file,' which adds the file type/extension meaning absent from the schema's generic 'Path' field. It could add more detail about absolute/relative paths, but the schema marks the parameter as required.

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 uses a specific verb 'Read' with a clear resource ('PowerPoint presentation') and states the outcome ('return slide content'). This differentiates it from sibling tools like read_word_document and read_excel_workbook, and from creation tools like create_presentation.

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 usage is implied through the name and resource: it should be used for reading .pptx files rather than Word or Excel files. However, the description provides no explicit guidance on when to use this tool versus alternatives or any caveats.

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