delete_alert_definition

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds value by stating the operation is irreversible and that active alerts generated by the definition are not deleted. It also clarifies the preview behavior (confirmed=False), which is not in annotations.

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 with a header, behavioral notes, and an Args section. Sentences are efficient and front-loaded. It could be slightly more concise, but the structure aids readability.

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 sibling tools and no output schema, the description covers the delete operation well. It explains return behavior (preview vs actual delete) and important side effects (active alerts untouched). It lacks explicit return format details, but the operation's outcome is clear.

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 coverage is 0%, so the description must compensate. It explains definition_id as a UUID, confirmed as a boolean defaulting to False (preview only), and target as an optional value from config. This adds meaningful context beyond the raw schema.

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 operation is a WRITE to permanently delete an alert definition, using the verb 'delete' and resource 'alert definition'. It distinguishes from sibling tools like create_alert_definition and list_alert_definitions by emphasizing permanence and irreversibility.

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?

The description gives explicit guidance on when to use (delete alert definitions) and notes that active alerts are unaffected. It also explains the preview behavior with confirmed=False. However, it does not mention when not to use or suggest alternative tools like set_alert_definition_state for disabling.

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