ds_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. It discloses one behavioral trait: the tool takes the schedule offline before deletion. However, it does not mention whether deletion is irreversible, what happens to related resources, or whether any confirmation is required. For a destructive tool, more disclosure is expected.

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 that efficiently conveys the core action and a key behavioral detail. Every word earns its place with no redundancy or filler.

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 simple delete operation with two parameters and no output schema, the description provides the bare minimum. It lacks information about return values, irreversibility, or any prerequisites. However, the parenthetical about taking offline adds a useful behavioral nuance, making it somewhat complete for a tool of this complexity.

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 does not mention any parameters. Schema coverage is 0%, so the description must compensate, but it doesn't. While the parameter names 'schedule_id' and 'project_name' are somewhat self-explanatory, the description adds no additional meaning or context about their roles or relationships.

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 with a specific verb+resource pair: "Delete a schedule." The parenthetical "takes it offline first" adds useful context about the deletion process and helps distinguish this from related sibling tools like ds_offline_schedule, which only takes a schedule offline without deleting it.

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?

The description implies the tool is for permanent removal of a schedule, and the mention of taking it offline first hints at a two-step process. However, it does not explicitly contrast with alternatives like ds_offline_schedule or state when to use delete vs. offline. No exclusions or prerequisites are provided.

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