model_wake

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

No annotations provided, so description carries full burden. It discloses WRITE operation with medium risk, resumes serving, notes undo limitation, and dev mode condition. Some edge cases (e.g., already awake) are unaddressed, but overall transparent.

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?

Description is front-loaded with practical info, using brackets [WRITE][risk=medium] and structured paragraphs. Could be slightly more concise but avoids unnecessary verbosity.

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 no output schema, the description does not explain return values. However, it covers core functionality, undo limitations, and conditional availability. Missing details on edge cases like already-wake state, but adequate for a wake action.

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 0%, so description must explain params. It does so clearly: 'dry_run: If True, preview without waking' and 'target: Inference target name from config; omit for the default.' Fully compensates for lack of schema 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 'Resume serving after Sleep Mode (weights return to GPU)' with a specific verb-resource combo, and distinguishes itself from sibling model_sleep by labeling itself as the inverse.

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 says when to use (inverse of model_sleep), when not to rely on undo, and suggests an alternative (call model_sleep with specific level). Also mentions conditional existence on servers with VLLM_SERVER_DEV_MODE=1, guiding proper usage.

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