remove_wake_rule

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

Adds context beyond annotations: renumbering after removal, permanent deletion. Annotations already mark destructiveHint=true, but description reinforces and explains behavior.

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 short paragraphs with no wasted words. Front-loaded with action, then steps, then alternative.

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 main usage and alternatives. Lack of output schema is fine. Could mention error cases (e.g., invalid index) but overall adequate for single-parameter tool.

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?

Single parameter 'index' is explained as identifier for the rule. Schema provides no description coverage, but description adds that index is used to select which rule to remove. Could specify starting index (e.g., 0-based) but not essential.

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 removal of wake rule by index. Distinguishes from siblings by referencing list_wake_rules for indices and set_wake_enabled for temporary disable.

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 tells when to use (permanent delete), prerequisite (list indices), and alternative (use set_wake_enabled for temporary disable).

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