add_wake_rule

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

Discloses mutation of wake rule configuration, persistence across restarts, and specifics about keyword and target_id behavior. Aligns with annotations (idempotentHint true) without contradiction.

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?

Concise, well-structured: first sentence states purpose, second clarifies usage with siblings, third gives parameter details. No wasted text.

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?

Covers purpose, usage, persistence, and key parameter semantics. Lacks mention of return value or behavior if rule already exists, but still fairly complete given no output schema.

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 has 0% coverage, but description adds meaning for target_id ('matches any source') and keywords ('empty list matches any message'). However, target_type and ignore_if_focused are not explained, leaving some ambiguity.

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 adds a wake rule that activates opencode on matching messages. It differentiates from siblings by naming related tools (list, remove, set_wake_enabled) for other operations.

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 states when to use this tool (to create rules) and provides alternatives for other operations (list, remove, toggle). Also clarifies persistence and default behaviors for empty/null parameters.

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