Cancel a scheduled instruction by its integer ID to abort it before execution. Solves the need to remove unwanted or outdated scheduled actions.
Cancel a Scheduled Instruction by integer ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Integer ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. 'Cancel' implies a state change, but the description does not state whether the action is idempotent, reversible, or what side effects occur. No information is given about what happens to the scheduled instruction or the expected response.
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, front-loaded sentence with no wasted words. It immediately conveys the action, the target resource, and the required identifier.
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?
The tool is simple with one parameter, and the basic action is stated. However, the absence of annotations, output schema, and any mention of effects or alternatives leaves gaps in fully understanding the behavioral context and when to choose this over related tools.
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 description coverage is 100%, and the single 'id' parameter is already described as 'Integer ID'. The description only restates this, adding no additional semantic 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 ('Cancel'), resource ('Scheduled Instruction'), and identifier type ('integer ID'). It is clear, but it does not differentiate this tool from its sibling 'scheduled_instructions_delete' or 'persistent_instructions_cancel'.
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 is provided about when to use this tool instead of alternatives. The sibling list includes scheduled_instructions_delete and persistent_instructions_cancel, and the description does not clarify the distinction between canceling and deleting a scheduled instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.