export_file

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It does not mention side effects like file overwriting, allowed formats, error behavior, or whether the entire scene or only selected objects are exported. The auto-detection note is the only behavioral trait disclosed.

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 two sentences, front-loaded with the core purpose and immediately followed by a useful parameter detail. Every word earns its place, with no redundancy or 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?

The tool is simple (2 parameters, no enums, output schema exists), and the description covers the essential purpose and the main parameter nuance. However, it leaves gaps such as scope of export, overwrite behavior, and relation to sibling tools, making it adequate but not fully complete.

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 must compensate. It explains the 'format' parameter (auto-detected from extension if null), which adds meaning beyond the schema's default. However, 'filepath' is left to its name, with no additional context about path handling or accepted formats.

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 uses a specific verb+resource ('Export the scene to a file'), clearly indicating the tool's function. However, it does not distinguish from sibling tools like export_selection or save_file, as it doesn't clarify scope (whole scene vs selection) or differences from similar operations.

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?

There is no guidance on when to use this tool versus alternatives such as export_selection or save_file. The only usage hint is 'Format is auto-detected from extension if not specified,' which is a parameter behavior, not a tool-selection guideline.

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