Delete an alert rule (org-scoped).

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

The description adds the scope context ('org-scoped') beyond what annotations provide (destructiveHint=true). However, it does not disclose other behavioral traits such as irreversibility, permission requirements, or side effects. Annotations already indicate the destructive nature.

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 extremely concise (one sentence), which is good for brevity, but it adds no information beyond the title. It is under-specified and does not earn its place as a valuable addition.

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?

Given the tool's simplicity (2 params, one required, output schema present) and its destructive nature, the description is minimally adequate. It covers the basic purpose but lacks details on what the response looks like or what constitutes a successful deletion.

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 input schema has zero description coverage for its two parameters (x-api-key, rule_id). The description provides no additional meaning or context for these parameters, forcing the agent to rely solely on the schema which lacks descriptions.

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?

Tautological: description restates name/title.

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 instead of alternatives like `alerts.update_rule` or `alerts.rule.get`. There is no mention of prerequisites or conditions under which deletion is appropriate.

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