delete_correlation_rule

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

Discloses critical behavior: irreversible action, silent removal of detection coverage, and the need for confirmation. No annotations were provided, so description fully carries this burden.

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 description with front-loaded main action and bullet-style parameter clarifications. Every sentence adds value; could be slightly more structured but remains clear.

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 key aspects: action, irreversibility, required confirmation, server targeting. Output schema exists so return values not needed. Omits error handling but acceptable for a delete 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?

Adds meaning beyond schema titles for confirm (must be True) and server (default active/default). Rule id is implicitly clear from the name and description. Schema coverage is 0% but description compensates well.

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 'Delete a correlation rule by id' with a specific verb and resource. Distinguishes from sibling tools like create_correlation_rule or set_correlation_rule_active by focusing on deletion.

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 explicit guidance on when to use (when permanent deletion is intended) and how to use (requires confirm=True). Does not explicitly exclude alternatives but implies finality.

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