delete_alert_definition

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds critical details: the operation is irreversible, active alerts from the definition are not affected, and the confirmed=False preview mechanism. This significantly enriches the behavioral model beyond what annotations alone convey.

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 well-structured and front-loaded with the core purpose, followed by essential caveats and a clean Args section. Every sentence provides valuable information without redundant padding.

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 description covers the tool's complexity fully: all parameters are explained, the destructive nature is clear, the preview/default flow is disclosed, and the alternative tool is suggested. There is no output schema, but the preview behavior is described, making the tool's behavior adequately specified.

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?

With 0% schema description coverage, the description carries the full burden and does so excellently. It explains definition_id as the UUID to delete, confirmed as requiring True to actually delete with a default of False for preview, and target as the Aria target name from config with a default.

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 opens with 'Permanently delete an alert definition,' using a specific verb and resource that clearly states the operation. It also notes 'Irreversible,' which distinguishes it from sibling tools like set_alert_definition_state that only silence a definition.

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?

It explicitly provides an alternative: 'Use set_alert_definition_state(enabled=False) instead to silence a definition you may want back.' The irreversibility warning and the preview default also communicate when not to proceed, making the usage context very clear.

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