snowflake_drop_pipe

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It does mention that confirmation is required, which hints at a safety mechanism, but it omits critical implications: whether the drop is permanent, whether it fails without confirmation, whether dependent objects are affected, or what the output/return value indicates. This is minimal beyond what the name implies.

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 extremely short and to the point, with no fluff. However, conciseness is undermined by under-specification; the two phrases are relevant but omit essential operational details. It is efficiently written but not fully 'earning its place' because critical context is missing.

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 complexity of 4 parameters, zero schema descriptions, no annotations, and no output schema details, the description is grossly insufficient. It fails to mention that the operation is destructive and potentially irreversible, does not explain the confirmation requirement clearly, and leaves the agent ignorant about how to specify the pipe, database, and schema. An agent cannot safely or correctly invoke this tool based on the description alone.

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 input schema has zero parameter descriptions, so the description must compensate, but it only mentions 'confirmation' without explicitly linking to the 'confirm' parameter or explaining the roles of pipe_name, database, and schema_name. It doesn't clarify that pipe_name is required, nor what database/schema defaults mean. Effectively no parameter semantics are provided.

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 states the specific action 'Drop' and the resource 'Snowpipe', which clearly distinguishes it from siblings like snowflake_create_pipe, snowflake_list_pipes, and snowflake_describe_pipe. The verb-resource pairing is unambiguous and matches the tool's name.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (like needing to stop ingestion first), and no exclusions. The only hint is 'Requires confirmation', which is a usage condition rather than a comparative guideline. It doesn't mention any conditions under which dropping a pipe might be inappropriate or what to check beforehand.

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