Remove an existing scheduled cron job by providing the exact cron expression and command. Ensures precise deletion without affecting other entries.
Remove a scheduled cron job. Must match an existing entry's cron_expression and command exactly (see ecp_crontab_list).
| Name | Required | Description | Default |
|---|---|---|---|
| command | Yes | ||
| confirm | Yes | ||
| cron_expression | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral burden. It does disclose exact-match semantics and implies no wildcarding, but it does not explicitly state irreversibility, what happens on no match, or the role of the confirm flag.
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, focused sentences with no filler. The exact-match constraint and the list reference are front-loaded and directly support correct use.
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 three-parameter removal tool, the description gives the missing operational essentials: match an existing entry exactly and use ecp_crontab_list to get the values. It is adequate for selecting and invoking the tool, though error/no-match behavior is not covered.
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 meaning to cron_expression and command by defining them as an exact-match pair against an existing entry, which is genuinely useful beyond the schema. But it gives no additional meaning to confirm, and schema coverage is 0%, so compensation is partial.
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 ("Remove") and resource ("scheduled cron job"), and it points to ecp_crontab_list as the companion lookup tool, making it clearly distinct from ecp_crontab_add and ecp_crontab_list.
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?
It explicitly instructs the caller to match an existing entry's cron_expression and command exactly and references ecp_crontab_list, giving clear preconditions. It does not explicitly contrast with ecp_crontab_add or state when not to use the tool, so it stops short of a full when/when-not map.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.