open_file

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

With no annotations, the description carries the full burden and does it well: it discloses the required capabilities (upload, plus state for confirmation), the destructive replacement of the current project, that LightBurn prompts to save unsaved changes, and that confirmation is only reliable for native formats otherwise reported as opened_unconfirmed.

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-loads the most important fact (capabilities and replacement behavior) in the first two sentences. The final sentence is long but each clause carries real information; only minor tightening is possible.

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 destructive, zero-required-parameter tool with no annotations and no output schema, the description covers prerequisites, side effects, timing behavior, and the possible success/opened_unconfirmed outcomes. Nothing essential for a correct call is missing.

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%, so the baseline is 3, but the description adds value by explaining the trade-off between path and content/content_base64 with a filename, and that the filename extension selects the importer. It reinforces rather than duplicates the schema wording.

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 effect ('REPLACES the current project with the file, like File > Open'), which precisely separates it from the sibling upload_file that merely uploads. The File > Open analogy makes the semantic outcome unmistakable.

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?

Gives concrete routing rules: send a local file via path, or content/content_base64 with a filename. It implies the difference from upload_file via the capability and replacement semantics, but never explicitly tells the agent when to use upload_file instead.

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