Snowflake Drop Task

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the danger profile is covered structurally. The description's only added value is the confirmation requirement, which meaningfully explains the confirm parameter's default of false. It still omits what is destroyed (task definition only, or dependent tasks/run history) and whether the operation is reversible.

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, zero wasted words, with the destructive action and the confirmation gate front-loaded. Structure is ideal for a simple drop tool.

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?

An output schema exists and annotations cover the safety profile, so the description needn't explain return values. But for a destructive, 4-parameter tool with 0% schema description coverage, the description is too thin: it never explains the database/schema scoping parameters or any preconditions like suspending 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 description coverage is 0% across 4 parameters, so the description must carry the load. It only hints at the confirm parameter; task_name, database, and schema_name—including whether database/schema context is required or defaults to the session context—are completely unexplained.

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?

States a specific verb (drop) and resource (task) in Snowflake, which cleanly separates it from create_task, suspend_task, resume_task, and describe_task in the sibling list. It does not explicitly name a sibling alternative, but the action is unambiguous.

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 useful usage context. However, it gives no when-to-use vs. alternatives guidance, no warning to check dependents or to suspend the task first, and no mention of irreversibility or undrop options.

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