model_load

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

Describes return value (model info or error message) and the set_current parameter effect, but does not disclose side effects, dependencies, or whether it overwrites existing models. No annotations provided, so description carries the burden but is only partially complete.

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?

Concise, front-loaded summary, with clear Args and Returns sections. Every sentence is necessary and no 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 simple load operation, it covers key aspects: parameters, return value. Could mention prerequisite of an active COM connection (comsol_connect) and potential error states, but overall adequate.

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?

Provides meaningful descriptions for both parameters beyond the input schema (which had only titles): explains file_path as absolute/relative path to .mph file, and set_current as whether to set as current active model with its default. Schema coverage was 0%, so description fully compensates.

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?

Clear verb 'Load' and resource 'COMSOL model' with source '.mph file'. Distinct from siblings like model_create and model_clone.

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 explicit guidance on when to use this tool vs alternatives like model_create or model_clone. Does not mention prerequisites (e.g., need an active COM connection from comsol_connect).

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