delete_alert_definition

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

Describes the operation as a WRITE and permanent, aligning with destructiveHint=true. Adds important context about side effects (active alerts not affected), going beyond 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?

Very concise (under 70 words), front-loaded with purpose, and well-structured with header and Args block. No unnecessary sentences.

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?

For a delete operation with no output schema, the description covers purpose, parameters, and key behavioral aspect (active alerts not affected). Complete for its simplicity.

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 0%, but the description's Args section provides clear definitions: definition_id as UUID, target as optional defaulting to config value. Adds meaning beyond type info.

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 starts with '[WRITE] Permanently delete an alert definition,' clearly stating the action (delete) and resource (alert definition), distinguishing it from siblings like create_alert_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?

Explains that the operation is permanent and that active alerts are unaffected, providing clear context for when to use. Does not explicitly name alternatives but purpose is clear.

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