Delete a scan schedule by providing its ID. Removes the specified schedule from the system.
Delete a scan schedule.
Args:
schedule_id: The ID of the scan schedule to delete
| Name | Required | Description | Default |
|---|---|---|---|
| schedule_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It does not disclose irreversibility, side effects (e.g., canceling future scans), or required permissions, which are critical for a deletion tool.
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?
Extremely concise with one sentence and one argument definition. No superfluous content, well-structured for quick parsing.
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 simple delete operation with an output schema (presumably present), the description covers the basic action. But it omits typical return behavior, idempotency, and error scenarios, leaving gaps for an agent.
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 description adds the purpose of the single parameter ('The ID of the scan schedule to delete'), which is helpful given 0% schema coverage. However, it does not specify format, source, or validation rules.
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?
Clearly states the verb 'Delete' and resource 'scan schedule', making the action unambiguous. However, it lacks differentiation from sibling tools like cancel_scan, though the distinct resource types mitigate confusion.
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?
No guidance on when to use this tool versus alternatives. Does not mention prerequisites, such as the schedule being in a deletable state, or what happens to associated scans.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.