Delete up to 100 scheduled downtimes at once to clean up monitoring configurations efficiently. Requires write permission for the operation.
Delete multiple SDTs at once (max 100, requires write permission)
| Name | Required | Description | Default |
|---|---|---|---|
| sdt_ids | Yes | SDT IDs (max 100) |
Changes observed during successful MCP inspections.
v4.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover destructiveness, read-only status, and idempotency, so the description only needs to add extra behavioral context. It adds the write-permission requirement and confirms batch semantics, which are useful beyond the 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 one compact, front-loaded sentence that conveys the action, scope, limit, and permission requirement with no filler or redundancy.
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 bulk delete tool with rich annotations covering safety and idempotency, this description is sufficient. It provides the core action, a batch limit, and a permission prerequisite, with no output schema requiring return-value explanation.
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 already documents sdt_ids as an array of strings with a max of 100, and the description merely repeats the max-100 constraint. No additional format, meaning, or edge-case guidance is provided, so it does not add value beyond the 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 states a specific verb ('Delete'), a specific resource ('SDTs'), and a clear scope ('multiple at once'). This distinguishes it from the single-item sibling delete_sdt and the device-targeting bulk_delete_devices.
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 phrase 'multiple SDTs at once' clearly signals when this tool should be used, and the 'max 100' cap adds a practical boundary. It does not explicitly name alternatives like delete_sdt for single deletions, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.