Snowflake Drop Stream

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 agent knows this is a destructive write operation. The description adds the confirmation requirement, which is useful behavioral context, but it does not disclose irreversibility, permissions, or what else may be affected.

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 two short sentences with no wasted words, and the core action is front-loaded. The second sentence is vague but still appropriately concise rather than bloated.

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?

This is a destructive operation with four parameters, 0% schema description coverage, and an output schema. Annotations cover the safety profile, but the description does not explain parameter semantics, scope, irreversibility, or confirmation behavior beyond a brief mention, leaving important context missing.

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 four parameters, so the description carries the burden of explaining them. It implies stream_name and confirm through 'Drop a stream' and 'Requires confirmation,' but says nothing about database or schema_name, leaving half the parameters with no meaning beyond their names.

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 a specific verb and resource: 'Drop a stream.' This is clear and distinguishes it from sibling tools that drop other objects, but it does not explicitly differentiate it from stream-related alternatives such as snowflake_create_stream, snowflake_undrop_stream, or snowflake_list_streams.

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 is a prerequisite rather than a usage guideline. It does not say when to use this tool versus alternatives like snowflake_undrop_stream or snowflake_create_stream, nor does it describe when dropping a stream is appropriate.

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