Load a model file

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

Adds valuable behavioral details beyond the minimal annotations: describes host path requirement, accepted file formats, the waiting behavior for large STEP files, and the M4a hardware requirement. Does not contradict annotations, though it does not specify what happens to existing plate contents (but destructiveHint=false implies non-destructive).

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 concise sentences with no redundancy. The core action is front-loaded, followed by format details and a performance note.

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 simple one-parameter tool with no output schema and minimal annotations, the description covers purpose, path semantics, file types, performance expectations, and a hardware prerequisite. Sufficient for correct invocation.

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's single parameter 'path' has no description (0% coverage). The tool description compensates by clarifying it is a path on the OrcaSlicer host and enumerating accepted formats, adding meaning the schema lacks.

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 action: 'Load a model file onto the current plate,' with a specific resource and target. It also lists accepted formats, distinguishing it from sibling tools like delete_object or transform_object.

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 clear context on when to use (loading a model from a host path onto the plate) and file format caveats. It does not explicitly exclude alternatives or mention sibling tools, but the context is sufficient for an agent to judge applicability.

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