set_wake_config

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

Annotations provide idempotentHint=true and readOnlyHint=false. The description adds that changes 'take effect immediately' and are 'persisted across restarts,' which goes beyond the annotations. However, it does not disclose potential side effects, permission requirements, or rate limits.

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?

The description is concise (~80 words) and well-structured: it starts with the overall purpose, then explains each parameter, and ends with behavioral notes. Every sentence adds value with no redundancy.

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 the tool's simplicity (2 optional parameters, no output schema), the description covers the core functionality and persistence. It lacks explicit mention of what happens when both parameters are null (likely resetting to defaults), but this is a minor gap.

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?

Input schema has 0% coverage (no parameter descriptions), so the description fully compensates by explaining both parameters in detail: window_title_patterns are substrings for matching window titles, and focus_shortcut is a keyboard shortcut for focusing the input box. Examples are provided, adding essential meaning.

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 tool's purpose: 'Configure the wake target window and focus shortcut.' It uses a specific verb and resource, and the explanation of parameters distinguishes it from sibling tools like get_wake_config (read-only) and add_wake_rule (adds rules rather than setting config).

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?

The description does not provide explicit guidance on when to use this tool versus alternatives such as add_wake_rule or set_wake_enabled. It only describes what it does without context about appropriate scenarios or exclusions.

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