import_pptx

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

Describes the import process: reads PPTX, extracts design elements, creates new project, generates HTML preview. With no annotations, this adequately discloses core behavior, though some potential constraints (e.g., file size limits) are omitted.

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?

Compact yet comprehensive. Front-loaded with main purpose, followed by detailed behavior, post-import tool list, parameter descriptions, and return info. No wasted words.

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?

Covers input (file_path, project_id), process (extraction, project creation), output fields (JSON with project_id, num_slides, etc.), and follow-up tools. Missing edge cases like error handling, but overall sufficient for a complex tool.

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 0%, but the 'Args' section gives clear explanations: file_path requires absolute path; project_id is auto-generated if omitted. This fully compensates for the schema's lack of descriptions.

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?

Clearly states verb 'imports', resource 'PPTX file', and outcome 'converts to a design spec'. Distinct from sibling ingest tools by focusing on external 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?

Explains the tool's use case for importing PPTX files and lists subsequent tools to use. Does not explicitly exclude alternative approaches, but context is clear.

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