export_pdf

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

With no annotations, description reveals key behavioral trait: saves session before export. Also notes platform requirement. Lacks detail on side effects of overwrite parameter, but overall informative.

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?

Three concise sentences. First sentence states core function, second adds a behavioral detail, third covers requirements. No extraneous text, though could be slightly more structured.

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?

Covers purpose, prerequisites, and a key behavioral trait. Missing details on return value or success indication, and no elaboration on parameter formats given lack of output schema. Adequate but not comprehensive.

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 has 0% description coverage. Description adds context for sheet parameter (workbook or one sheet) but does not explain pdf_path format, overwrite behavior, or session_id purpose. Partially compensates.

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?

Description clearly states verb 'export' and resource 'workbook (or one sheet)' to PDF, distinguishing from sibling export tools like export_csv and export_json.

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?

Provides prerequisites (Excel on Windows, uv sync --extra com) and notes the tool saves the session first. Does not explicitly contrast with alternative export methods but implies PDF-specific use.

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