tosea_pdf_to_presentation

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

No annotations are provided, so the description bears the full burden. It explains parameter dependencies and constraints but does not disclose error handling, idempotency behavior (despite containing an idempotency_key parameter), rate limits, or potential destructive actions. The tool likely creates files but not explicitly stated as non-destructive.

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 paragraph that front-loads the main purpose and provides key usage notes. It is moderately concise but includes a redundant opening phrase. Every sentence adds value, though some could be merged for brevity.

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 14 parameters, 0% schema description coverage, and no output schema, the description is incomplete. It fails to explain critical inputs like file_paths, instruction, export_filename, and many rendering options. The tool's complexity demands more comprehensive documentation.

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 must compensate. It explains 4 parameters (slide_mode, template_file_id, logo_file_id, output_format) but leaves 10 parameters unexplained (file_paths, instruction, export_filename, render_provider, render_model, image_model, slide_domain, page_count_range, template_name, idempotency_key). This is a significant gap.

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 clearly states the tool's function: 'Upload local source files and generate a final export in one shot.' This distinguishes it from sibling tools like tosea_parse_pdf or tosea_export_presentation, which are single-step operations.

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 gives explicit guidance for parameter usage: defaults for slide_mode, when to use slide_mode='image', constraints on template_file_id and logo_file_id, and advice for output_format='pptx_image'. However, it does not explicitly compare to sibling tools for when to use this one-shot approach versus composing manual steps.

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