load_model

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

Disclosures that it sets the active model state, consistent with idempotentHint=true. No contradictions with annotations. Adds context about file sources but does not detail side effects (e.g., overwriting unsaved changes).

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?

Two concise sentences with front-loaded action verb and clear parameter guidance. No unnecessary words.

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?

With output schema present, description adequately covers the loading operation. Could mention effect on existing model state, but siblings like new_model imply this is a replacement.

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%. Description adds mutual exclusivity constraint and clarifies the distinction between file_path and upload_name, which goes beyond the schema's individual parameter descriptions.

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 verb 'Open' and the resource 'IDF or epJSON file as the active model'. It distinguishes from siblings like new_model and save_model by specifying it loads an existing file.

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?

Explicitly instructs to 'Provide exactly one source: file_path or upload_name', guiding parameter selection. Does not explicitly state alternatives (e.g., new_model for creating a new file), but context is clear for a loading action.

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