export_scene

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

With no annotations, the description carries the full burden and does so well: it discloses that the file lands on the SketchUp host, that the path is unreadable on a split-host setup, and that skp export from a never-saved model emits a warning tied to SketchUp binding the live document to the export path. It omits overwrite behavior and any permission requirements, keeping it short of a 5.

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?

Front-loaded with the core action, then cleanly segmented into "Formats:" and "Returns:" blocks; nothing is padding. The formats line duplicates the enum description in the schema nearly verbatim, which is a minor redundancy.

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 single-parameter tool with an output schema, the description supplies everything the schema cannot: host-side file location, the split-host readability caveat, and the meaning of the conditional "warning" field. An agent has all it needs to call this correctly and relay results.

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 coverage is 100% with an enum, so the baseline is 3, but the description adds information the schema lacks — the default 1920×1080 viewport resolution for png/jpg. The format grouping itself largely restates the schema's own enum description.

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?

States a specific verb and resource ("Export the current scene to a temp file") and enumerates supported output formats, so the agent knows exactly what is produced. It does not, however, differentiate itself from the closest sibling get_viewport_screenshot, which also yields image output via the png/jpg formats.

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?

Usage is implied by the format list and the temp-file destination, giving the agent a reasonable sense of when a file export is appropriate. There is no explicit when-not guidance, no prerequisites, and no pointer to alternatives such as get_viewport_screenshot for viewport captures.

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