delete_scheduled_maintenance

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

No annotations are provided, so the description carries the full burden. It discloses the deletion action but omits any information about irreversibility, side effects on associated data, or whether the operation is a hard delete. For a destructive tool, this is a significant transparency gap.

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 a single, direct sentence that immediately states the action and target. It contains no filler or redundant information, achieving maximum conciseness while remaining clear.

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 the tool's simplicity (one parameter, clear output schema), the description is largely complete. It does not need to explain return values due to the output schema. However, a brief mention of the ID's origin (e.g., from list_scheduled_maintenance) or irreversible nature would enhance completeness, so it falls just short of a 5.

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?

The schema covers 100% of the parameter, and the maintenance_id property already has a clear description ('Scheduled maintenance ID to delete'). The tool description adds no extra semantic value beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Delete') and resource ('scheduled maintenance window') combined with an ID reference, making the tool's function unambiguous. It also clearly distinguishes from sibling tools like create_scheduled_maintenance and list_scheduled_maintenance.

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 intended usage is implied by the tool name and description, but there is no explicit guidance on when to use it versus alternatives, nor any mention of prerequisites or exclusions. It only states the action without context such as 'use this to remove an existing window' or 'not for editing.'

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