preview_3d

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

Discloses output (file path and viewer URL hint) and requirements, but does not mention side effects like file creation or overwriting, which is relevant for a file-exporting tool.

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 sentences, no wasted words, front-loaded with purpose. Efficiently communicates essential 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?

Covers purpose, output, and requirements but lacks parameter details and usage context compared to siblings. Incomplete for a tool with 4 parameters and no schema descriptions.

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?

With 0% schema description coverage, the description adds no information about parameters like 'file_path', 'field_name', 'timestep', or 'output_filename'. Parameter names are somewhat self-explanatory but the description should clarify their roles.

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?

Clearly specifies 'Export dataset to glTF/glB for interactive 3D viewing in a browser.' Uses specific verbs and resources, distinguishing it from siblings like render or volume_render.

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 a clear prerequisite (VTK >= 9.4 with vtkGLTFExporter support) but does not explicitly state when to use vs alternatives or when not to use.

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