Tasks Drop Task

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety bar is lower. The description adds one genuine behavioral detail, that a confirmation is required, but it omits what happens if confirm is false, that the drop is irreversible, and that no undrop_task sibling exists to recover from it.

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?

Two short sentences with zero filler, and the destructive action is front-loaded ahead of the precondition. Nothing could be removed without losing content.

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?

With a rich annotation set and an output schema, the description needn't explain returns. But for a destructive tool with a confirm gate and no undrop counterpart among the tasks_* siblings, an agent would benefit from knowing the drop is permanent and how to recover or recreate the task.

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 75%; the database, task_name, and schema_name params carry quoting guidance in the schema, but confirm has no schema description at all. "Requires confirmation" explains confirm's purpose, which is real added value, though it doesn't state the semantics of confirm=false versus confirm=true.

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?

"Drop a task in Snowflake" is a specific verb+resource that unambiguously separates it from tasks_suspend_task, tasks_resume_task, and tasks_execute_task. It stops short of naming any sibling or scope qualifiers, so it does not fully earn 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?

"Requires confirmation" implies a precondition for invocation, which is actionable guidance for the confirm parameter. However, it gives no explicit when-to-use vs. alternatives guidance, and it doesn't tell the agent whether to first call tasks_describe_task to verify it's targeting the right object.

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