load_model

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether loading replaces the current model, whether there are side effects on existing data, or what occurs on an invalid path. 'Load a .mph model from disk' names the operation but omits its consequences.

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 a single sentence with no filler or redundant phrasing. It is efficiently front-loaded with the action and resource, though its brevity sacrifices useful context that could be added at minimal length cost.

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 state-changing tool with one parameter and no annotations, this description is too sparse. It lacks any mention of expected output, side effects, preconditions, or error behavior, so an agent cannot fully anticipate the impact of calling it.

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%, yet the description does not explain the 'path' parameter's expected format, whether relative paths are accepted, or how the extension is handled. It merely implies the path points to a .mph file, adding marginal value beyond the schema's 'Path' title.

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 ('Load') and a clear resource ('.mph model from disk'), making the core action unmistakable. It operationally differs from siblings like save_model or new_model, though it stops short of explicitly naming them.

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?

No guidance is provided on when to use this tool versus alternatives such as new_model, generate_model_java, or import_geometry. The description states only the action, not the circumstances that should trigger its use or when it is not appropriate.

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