load_model

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

Discloses key behavior (loading into memory, keepAlive, provider default) but omits details like idempotency, errors, authentication needs. No annotations to supplement.

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, front-loaded with core purpose, no filler.

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?

Adequate for a loading tool: covers main behavior and options. No output schema needed. Could mention return status or loading duration, but not essential.

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?

Adds meaning beyond 100% schema coverage: keepAlive format hint and provider default behavior. Baseline 3, plus additional context.

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?

Clearly states verb 'load', resource 'model', and purpose 'ready for inference'. Distinguishes from siblings like unload_model, list_models.

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 context for provider argument ('without a provider arg, loads on every detected provider'), but lacks explicit when-not-to-use or alternatives like complete/embed.

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