Generate a base64 PNG thumbnail of a Tableau workbook from a .twb or .twbx file. Visually verify your workbook's layout and content before publishing.
Return a thumbnail image (base64 PNG) of a generated Tableau workbook.
| Name | Required | Description | Default |
|---|---|---|---|
| workbook_path | Yes | Absolute path to the .twb or .twbx file to preview. |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It clearly states the output (base64 PNG) and the input context (a generated workbook), but it does not mention whether the operation is read-only, what happens if the path is invalid, or any size/format limitations of the thumbnail.
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 that states the purpose and output format without redundancy. Every word contributes meaning and there is no filler.
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?
For a tool with one well-documented parameter and no output schema, the description covers the essential return type and input. It could be more complete by noting error behavior or side-effect-free nature, but the low complexity keeps the gap small.
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%: workbook_path is already described as an absolute path to a .twb or .twbx file. The description adds only the context that the workbook is 'generated', which is minor beyond the schema's own meaning.
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 states a specific verb ('Return'), a specific resource ('generated Tableau workbook'), and the output format ('thumbnail image (base64 PNG)'). This clearly distinguishes preview_workbook from siblings like generate_workbook, publish_to_cloud, and profile_dataset.
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 word 'generated' implies the tool is used after generate_workbook, and the thumbnail format suggests a preview step before publishing. However, it never explicitly says when to use it versus alternatives, nor does it mention exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.