Permanently remove a scheduled job discovery cron job using its ID. List schedules first to find the correct ID.
Permanently delete a scheduled job discovery cron job by its ID. Use list_schedules to see available IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Schedule ID to delete |
Changes observed during successful MCP inspections.
v3.2.5Does 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 key trait that the deletion is permanent/irreversible. It says nothing about permissions required, behavior on an unknown ID, or whether a running job is stopped, which leaves meaningful gaps for a destructive operation.
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 short sentences with zero padding, and the permanence warning plus the ID-sourcing hint are both front-loaded.
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 single-parameter destructive tool with no annotations or output schema, the description covers the essential facts: what is deleted, that it is permanent, and where to get the ID. Only edge-case behavior (invalid ID, running job) is unaddressed.
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% with a single documented parameter, so the schema already defines 'id' fully. The description reinforces that the ID comes from list_schedules, adding mild value but no syntax or format detail 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?
States a specific verb (delete) and resource (scheduled job discovery cron job), plus the identifier used to target it. An agent can distinguish it from delete_all_schedules and toggle_schedule without opening any 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?
Explicitly points the agent to list_schedules to obtain valid IDs, which is a genuine usage prerequisite. It does not state when to prefer this over delete_all_schedules or what happens if the schedule is currently active, so it stops short of full when/when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.