install_model

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

No annotations provided, yet description covers key behaviors: no restart needed, async continuation, and trust/whitelist source. Lacks specifics on error handling or permissions, but provides substantial transparency for a tool with zero annotation coverage.

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 sentences, no redundancy, front-loaded with the main action. Every sentence adds value: the how, the constraints, and important behavioral notes.

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?

Given existence of output schema (not shown), return values need not be explained. The description covers parameter source, folder destination, async behavior, and verification step. Could mention failure modes, but overall adequate for context.

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?

Only one parameter 'name' with 0% schema description coverage. The description adds crucial semantic context: the name must be an exact catalog name from search_models. This compensates well for the bare schema.

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 (download/install), the resource (model from catalog), and the destination (models/<type>/ folder). It distinguishes from nodes (no restart needed) and references sibling tool search_models for exact name, making intent and scope unmistakable.

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 tells to use exact name from search_models and to verify with list_models after completion. Also warns about large model download times and server-side continuation. Does not explicitly say when not to use, but the context is clear enough.

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