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

Without annotations, the description carries the full burden. It details the rule's reactivity and the available triggers/actions, but doesn't disclose whether the rule becomes active immediately, any permission requirements, or what the response contains. This is a moderate level of transparency.

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: three short sentences. The main purpose is front-loaded, followed by scannable lists of triggers and actions, with no filler or 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?

The tool has nested objects for conditions and actions, plus priorityOrder, but the description only covers triggers and actions. It omits optional conditions, priority order, and targetId scope. Since there is no output schema, the return value is also unspecified. The schema covers these, but for a moderately complex create operation, a fuller overview is expected.

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?

The schema already provides 100% parameter coverage, but the description adds extra meaning by explaining each action type (e.g., escalate changes severity, suppress mutes, rerun schedules a retry). This enriches the bare enum values with practical semantics.

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 it creates an automation rule that reacts to events, and lists the specific triggers and actions. It is specific and informative, but it doesn't explicitly differentiate from sibling tools like create_muting_rule or create_notification_rule.

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?

Provides clear context by enumerating the supported triggers and actions, making it evident when to use this tool. However, it doesn't mention exclusions or alternative tools for specific scenarios, so it stops short of a 5.

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