scheduler_delete

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

The description indicates 'permanently delete', which implies irreversibility, but no additional behavioral traits are disclosed (e.g., permissions needed, cascading effects, success/failure behavior). With no annotations, this is minimal but acceptable for a delete operation.

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 concise sentence that effectively communicates the core functionality. It is front-loaded with the key information, though it could include a slight additional detail without becoming verbose.

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 simplicity (one parameter, clear destructive action), the description is adequate. The presence of an output schema covers return values. However, a note about irreversibility or existence check would enhance completeness.

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 coverage is 100%, so the schema already documents task_id as a required string. The description adds no extra meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 'Permanently delete a scheduled task', specifying the verb 'delete' and the resource 'scheduled task'. It is distinct from sibling tools like scheduler_create, scheduler_list, and scheduler_pause, which have different actions.

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 on when to use this tool versus alternatives. No mention of preconditions (e.g., task must exist), or that deletion is irreversible. The description only states what it does, leaving the agent to infer usage context.

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