disable_automation_rule

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

With no annotations, the description carries full burden. It states the tool disables a rule without deletion, which implies a state change (mutation) but doesn't disclose permissions needed, whether the change is reversible, side effects, or error conditions. Minimal behavioral context is provided.

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 a single, efficient sentence that front-loads the core action and adds a clarifying constraint ('without deleting it'). Zero waste, appropriately sized for the tool's simplicity.

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?

For a mutation tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, or output. Given the tool's straightforward nature, it's passable but leaves gaps in guidance and transparency.

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 description coverage is 0%, but the single parameter 'ruleId' is self-explanatory. The description doesn't add any parameter details beyond what the schema name implies. Baseline is 3 since the parameter is simple and the schema covers it structurally, though no semantic enrichment is offered.

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 action ('Disable') and the resource ('an automation rule'), and specifies the effect ('without deleting it'). It distinguishes from 'delete_automation_rule' by noting preservation, but doesn't explicitly differentiate from 'enable_automation_rule' or other rule-related tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'enable_automation_rule', 'update_automation_rule', or 'delete_automation_rule'. The description implies it's for temporarily deactivating rules, but lacks explicit context or prerequisites.

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