delete_schedule

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a scan schedule' implies a destructive operation but does not mention side effects, such as whether associated scans are canceled, whether the deletion is reversible, or if any confirmation is required. This lack of transparency is a notable gap for a mutation 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?

The description is a single, clear sentence that conveys the tool's purpose without any redundant or extraneous information. It is appropriately sized for a simple delete operation, and every word contributes meaning.

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?

While the tool is simple (one parameter, no output schema), the description is minimal and lacks critical contextual details such as side effects, reversibility, or relationship to schedules and scans. Given the absence of annotations and output schema, the description is incomplete for a destructive operation.

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 input schema fully documents the only parameter (schedule_id) with a description and UUID format, so the schema coverage is 100%. The description adds no additional parameter semantics, which aligns with the baseline score of 3 when the schema already provides complete parameter information.

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 action ('Delete') and the resource ('a scan schedule'), using a specific verb and noun. This unambiguously distinguishes it from sibling tools like list_schedules, create_schedule, and update_schedule.

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 on when to use this tool versus alternatives. For example, there is no mention of prerequisites, such as whether a schedule can be deleted if it is currently active, or any note about using delete_blackout for blackout schedules instead. The description offers no contextual usage cues.

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