Delete Maintenance

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

With no annotations, the description carries the full behavioral burden, and it does disclose the two most important traits of a destructive tool: the action is permanent and the affected monitors return to normal alerting afterward. It omits permission/auth requirements and any confirmation or rate-limit behavior, keeping it short of a 5.

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?

Three short sentences, front-loaded with the destructive verb and its permanence, then the side effect, then the ID lookup. No filler.

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 one-parameter destructive tool with an output schema (so return values need no explanation) and no annotations, the description covers permanence, downstream effect, and ID sourcing. Only authorization/permission expectations are missing.

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 100% for the single maintenanceID parameter, so the baseline is 3. The description adds real value beyond the schema by telling the agent where to obtain the ID (getMaintenanceWindows), which is the main failure mode for this call.

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?

States a specific verb and resource ('Permanently deletes a maintenance window') and immediately distinguishes itself from pauseMaintenance/resumeMaintenance by the word 'permanently'. An agent can tell what this does without opening the schema.

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 a workflow hint ('Use getMaintenanceWindows to find the ID'), which is genuinely useful for invocation, but it never states when to choose this over the sibling pauseMaintenance or what conditions make deletion appropriate. Usage is implied rather than framed as guidance.

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