get_pptx_slides

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

No annotations are provided, so the description carries full burden. It implies a read operation but does not explicitly state that the tool is non-destructive. It also fails to describe what 'content' includes (e.g., text only, images, formatting) or any side effects. This lack of detail limits transparency.

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 sentence, achieving conciseness. However, it could be more structured by including a brief hint about the return value or usage context. As is, it is neither verbose nor optimally informative.

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 tool has an output schema, the description does not need to explain return values. However, it does not clarify what 'with content' means or whether the output includes slide numbers, titles, or full text. The description is too sparse for an agent to confidently use the tool without inferring from the schema.

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 coverage is 100% for the single parameter 'file_path', which is already well-described in the schema. The description does not add any additional meaning or context about the parameter, so it provides no extra value beyond the schema.

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 the verb 'list' with the resource 'slides from a PPTX file', making the main purpose clear. Adding 'with content' hints at returning slide content, but it's ambiguous whether it returns full text or just metadata. It distinguishes from sibling tools like 'get_docx_paragraphs' and 'get_xlsx_sheets' by targeting PPTX files.

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 on when to use this tool vs alternatives. The description does not mention prerequisites (e.g., file must exist), safety (read-only), or when not to use it. Sibling tools like 'edit_pptx_slide_text' suggest different use cases, but the description offers no such context.

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