lora_load

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=true, so the safety profile is covered structurally. The description adds the [WRITE][risk=medium] classification and the 'hot-load' semantics (live engine, no restart), but does not disclose what happens on name conflicts, whether an existing adapter is evicted, or any permission requirements.

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?

It is front-loaded with the operation type and risk marker, then one purpose sentence, then a compact Args block. Every line earns its place, and the Args block is justified by the schema's zero description coverage.

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 mutation tool with annotations but no output schema, the definition covers purpose and all parameters adequately. However, behavioral gaps remain for a medium-risk hot-load operation: conflict/replacement behavior, interaction with lora_unload, and any effect on engine state or memory are unstated.

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%, so the description must carry the full parameter burden, and it does: lora_name as the name to register, lora_path as a local path or HF repo id, and target as a config-defined inference target with 'omit for the default' behavior. Every parameter gains meaning not present in the bare schema titles.

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 states a precise verb and resource: 'Hot-load a LoRA adapter onto the running engine,' which is clearly distinct from sibling operations like model_deploy or lora_unload. It does not explicitly name or contrast those siblings, so it lands at clear-but-no-differentiation.

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?

Usage is only implied: 'Hot-load ... onto the running engine' suggests the engine must already be running and that this adds an adapter without a redeploy. There is no explicit when-to-use vs lora_unload/model_deploy guidance, no prerequisites, and no exclusions.

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