Load a model file

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

The description goes beyond the minimal annotations by disclosing accepted file formats and version-specific STEP support. It also notes that large STEP files can take a minute to tessellate and that the call waits, which gives the agent a realistic expectation of blocking behavior. This is valuable context the annotations do not provide.

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 exceptionally concise, packing the core action, supported file types, and a performance caveat into two sentences. Every clause adds value, and the main action is front-loaded, making it easy for an agent to quickly understand what the tool does.

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 no output schema, the description is largely sufficient. It covers the operation, accepted formats, and potential blocking for large STEP files. However, it does not explicitly mention what the tool returns after loading or whether it replaces or adds to the current plate, which leaves a small but non-critical gap.

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?

The schema only defines a 'path' string with no description, so the description adds crucial meaning by clarifying the path is on the OrcaSlicer host and listing how the available formats, suggesting what file types are acceptable. While it could be more explicit about path format (absolute vs. relative), it compensates well for zero schema coverage.

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 clearly states the tool loads a model file from a host path onto the current plate, using a specific verb and resource. It distinguishes itself from sibling tools like delete_object or transform_object by focusing on the import action. The added list of supported formats further sharpens its scope.

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 description provides clear context: use this tool to import supported model files from the host into the current plate. It also includes the useful caveat that large STEP files may cause a wait. Although it doesn't explicitly mention alternatives or when not to use it, the purpose is unambiguous enough for a single-purpose load tool.

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