create_pdf

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write/safety profile is covered. The description adds a real environmental prerequisite (LibreOffice required for office formats), but says nothing about how 'overwrite' behaves, whether the output path's directory must exist, or what happens on partial failure.

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: the action and artifact come first, the accepted formats follow, and the LibreOffice caveat is tucked into a parenthetical. No filler, nothing that could be dropped without losing information.

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?

An output schema exists, so return values need not be described. Given that, the description covers the essential contract for this tool: what it produces, what it accepts, and the one blocking environment dependency. The remaining gap is parameter-level detail, which is scored separately under parameter semantics.

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%, so the description carries the full burden for three parameters, yet it names none of them. It partially compensates for 'sources' by listing accepted input formats (implying a list of file paths), but 'output' and 'overwrite' are left entirely undefined in both schema and prose.

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 and artifact ('Build one PDF') plus the exact source types it accepts, which cleanly separates it from PDF-only siblings like merge and split. It doesn't explicitly name which sibling to prefer, so it stops short of a 5, but an agent can still tell what this tool produces.

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 enumeration of Word/Excel/PowerPoint/ODF/image/text sources implicitly frames this as the cross-format conversion tool, distinguishing it from merge (PDF-in, PDF-out) and export. However, there is no explicit when-to-use statement, no mention of the alternative tools, and no note on limits such as how many sources may be combined.

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