set_rule_active

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

Annotations already disclose the meaningful behavior: readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds nothing beyond that — it does not say whether deactivation is reversible, what happens on an unknown rule_id, or whether the call returns the updated rule. For a mutation with no output schema, that silence leaves real gaps.

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?

A single short sentence with zero filler and the action front-loaded. It is efficient, though its brevity is achieved partly by omitting information rather than by tight editing.

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 is simple (two required params, no nesting, no output schema) and annotations cover the safety profile, so the bar is low. Even so, the description leaves unclear how the boolean active argument maps to activation versus deactivation, and says nothing about failure modes or the sibling update_rule, which is not enough for an agent to call it confidently.

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 50%: rule_id carries a UUID description, while active is a bare boolean with no description. The tool description never mentions either parameter, so it provides no compensation for the undocumented active flag or its relationship to the tool name.

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 names a specific verb pair and resource: 'Activate or deactivate a rule.' An agent can immediately tell this is a state-toggle mutation on a rule. It does not, however, distinguish this from the sibling update_rule, which could plausibly also change a rule's active state.

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?

There is no guidance on when to use this tool versus update_rule, nor any precondition such as the rule having to exist first. The only usage signal is the verb itself, which the agent must interpret unaided.

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