remove_scheduled_task

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, and the description does not disclose any behavioral traits beyond the operation. It doesn't state that the action is destructive, irreversible, what happens if the task doesn't exist, or whether confirmation is required. For a deletion tool, this is a significant transparency gap.

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 very brief: two lines. It is not verbose, and every sentence earns its place. However, it is minimal to the point of under-specification for a destructive operation, so I rate it 4 rather than 5.

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?

Given the tool's destructive nature, 1 parameter, and no annotation coverage, the description is insufficient. It does not cover error cases, side effects, or prerequisites. The output schema exists, so return values are not needed, but behavioral context is missing. Overall, the tool is minimum viable but with clear gaps.

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 has 0% description coverage for the 'name' parameter. The description says 'Name of the task to remove' but adds little beyond the parameter title. It doesn't specify format, validity, or how to discover valid names. Since coverage is 0%, the description should compensate but doesn't.

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 clearly states the tool's function: 'Remove a scheduled task.' It uses the specific verb 'remove' and identifies the resource, distinguishing it from sibling tools like create_scheduled_task and list_scheduled_tasks. However, it doesn't elaborate on what a scheduled task is or provide any scope context, so it's not a 5.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that tasks can be listed with list_scheduled_tasks before removal, nor does it state any prerequisites or exclusions. The only context is the operation itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.