export_chart_pdf

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

No annotations provided, so description carries the burden. It discloses the need for kaleido, the return value structure, and error condition. However, it does not explain side effects such as file save location, overwrite behavior, or validation of input figure. Transparency is adequate but incomplete.

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?

The description is extremely concise with two sentences plus a return line. Every word adds value: purpose, prerequisite, return structure, and error case. No fluff.

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 4 parameters, no annotations, and an output schema (context indicates its existence), the description covers the key aspects: purpose, prerequisite, return format, and error handling. It could mention file save location or naming conventions, but overall completeness is good for a well-parameterized tool.

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%, so baseline is 3. The description adds no additional meaning to parameters beyond what the schema already provides (e.g., width, height, filename, figure). The prerequisite note is not parameter-specific.

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?

The description clearly states 'Export a chart to PDF' with a specific verb and resource. It distinguishes from sibling export tools (export_data, export_to_datawrapper, export_visualization) by focusing on PDF format and including a prerequisite note about kaleido.

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?

No guidance on when to use this tool versus alternatives like export_visualization or export_data. The description mentions a prerequisite (kaleido) but does not provide context for selecting this tool over siblings.

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