Snowflake Drop Pipe

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write. The description adds one useful behavioral fact beyond the annotations — that a confirmation step is required — but omits irreversibility, the effect on the pipe's ingested data, and any permission requirements.

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, front-loaded with the action and followed by the single gating constraint. No filler, no repetition of the tool title.

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 so return values need no explanation, but for a destructive drop with 0% parameter documentation the description is thin: it never names the confirm parameter, warns of permanence, or explains how database/schema_name qualify the target pipe.

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% for 4 parameters, so the description must carry the load. It only obliquely references the confirm flag via 'Requires confirmation' and says nothing about pipe_name, database, or schema_name, leaving namespace qualification and the default-false confirmation behavior undocumented.

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 and resource ('Drop a Snowpipe'), which is unambiguous and clearly distinct from siblings like snowflake_create_pipe, snowflake_describe_pipe, and snowflake_get_pipe_status. It stops short of explicitly telling the agent when this is preferable to those siblings, but the purpose itself is crisp.

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 only guidance is 'Requires confirmation', which gestures at the confirm parameter but never says when to call this tool, what prerequisites exist (e.g., pipe must be suspended), or that there is no undrop_pipe sibling to reverse it. No alternatives or exclusion conditions are given.

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