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

Annotations already declare it as a non-read-only, non-destructive, closed-world operation, lowering the bar. The description adds the accepted-format set and that a result file is returned, but says nothing about limits (the 5-file / 50 MB cap lives only in the schema) or failure behavior.

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?

Two short sentences, zero waste, with the core action and accepted inputs front-loaded. Nothing extraneous.

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?

With no output schema, 'Returns the result file' is a minimal but useful return hint. However, for a conversion tool among many overlapping siblings, the description does not do enough to orient the agent on limits or alternatives.

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 description coverage is 100% and the single 'files' parameter is fully documented, including the upload_id vs content_base64 alternative and size limit. The description only restates the accepted formats already present in the schema, so it neither adds nor detracts.

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) and resource (presentations to PDF), and enumerates accepted input formats (pptx, ppt, odp, key). It does not distinguish itself from the sibling convert-office, which plausibly overlaps, so it falls short of a 5.

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 format list implies when the tool applies, but there is no explicit guidance on when to choose this vs convert-office or the various X-to-PDF siblings (word-to-pdf, excel-to-pdf). No exclusions or prerequisites are given.

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