convert_to_pdf

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

No annotations are provided, so the description carries the full burden. It does disclose a genuine behavioral trait beyond the schema: Office/HTML inputs require LibreOffice, which warns the agent about a possible failure mode. It says nothing, however, about whether existing files are overwritten, what the default output_path is, or what the return value/errors look like.

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, purpose front-loaded, dependency stated as a follow-up constraint. Every sentence earns its place and nothing is padded.

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 annotations, no output schema, and 0% schema coverage, the description should carry more. It covers the conversion capability and one dependency, but omits overwrite semantics, output_path defaulting, and return/failure behavior, leaving an agent to guess on two of three parameters.

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 0% across 3 parameters, so the description must compensate. It partially covers input_path by naming the accepted input formats, but leaves output_path and overwrite entirely undefined, including the meaning of the null defaults.

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 (Create) and resource (PDF) and enumerates the accepted input kinds: image, text/markdown, Office/HTML document. That is clear enough to know what the tool produces. It does not, however, differentiate itself from the sibling images_to_pdf, which overlaps on the image case.

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?

There is no explicit guidance on when to use this tool versus alternatives, and the obvious overlap with images_to_pdf is never addressed, so an agent cannot tell which to pick for an image input. The only conditional content is a runtime dependency (LibreOffice), which is a prerequisite rather than usage routing.

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