Convert presentations

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered; the description is consistent with that. It adds the useful context that inputs may be a single file, a list, or a whole folder, but says nothing about whether existing outputs are clobbered, how large batches behave, or what is returned. No contradiction with annotations.

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?

A single front-loaded sentence that begins with the verb and then enumerates inputs and outputs; dense but every clause carries information. Slightly long for one sentence, though nothing is redundant.

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 a non-read-only file-producing tool with no output schema, the description does the essential work of spelling out the full input/output format matrix that an agent needs to pick valid formats values. Remaining gaps (overwrite semantics, return payload) are either covered by the schema (overwrite) or minor for a conversion utility.

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 64%, and the description usefully explains the formats enum (pptx, pdf, deckcraft, png/jpeg, outline) and the pdf layout options (slides/notes/handouts) at a high level. It leaves scale, suffix, overwrite, output_dir/output_path, handouts_per_page, and input_dir/input_paths unaddressed, so it only partially compensates for the coverage 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?

States a specific verb (convert) plus the resource (presentations), and enumerates both accepted input formats (.pptx, .deckcraft) and every output format, so an agent knows exactly what the tool produces. It does not, however, differentiate itself from the overlapping sibling render_slides, which likely also turns slides into images.

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 lists capabilities but never says when to choose this tool over render_slides, edit_presentation, or create_presentation, nor any precondition (e.g. file must already exist, output_dir needed for new files). Usage must be inferred purely from the format list.

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