maintenance_delete

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

Adds value beyond the destructiveHint annotation by specifying that alert generation resumes and historical suppression is retained for already-passed periods. This gives agents a precise mental model of the side effects.

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?

Two tightly written sentences convey purpose, immediate effect, and a retention nuance without any fluff. Front-loaded with the verb and resource.

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 what happens after deletion (immediate alert resumption) and a critical edge case (historical retention for passed periods). With an output schema present and destructiveHint annotation, no critical information is missing for correct invocation.

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 100% since the only parameter (maintenanceids) is documented in the schema itself. The description does not add parameter-level meaning beyond what the schema already provides.

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

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 explains the effect of deletion (canceling alerts) but doesn't explicitly say when to use vs alternatives. However, the resource and verb make it clear versus maintenance_get/create/update siblings.

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