Streams Drop Stream

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is largely carried by structured data. The description's 'Requires confirmation' adds real value by signaling a two-step gate the agent must satisfy. However, it omits the important behaviors: whether drop is permanent, what happens to downstream consumers, and whether the operation can be recovered.

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, with no filler. It is minimal but not padded, and the confirmation constraint is placed where it will be read.

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, non-idempotent operation on a 4-parameter tool, and the description does not address irreversibility, cascade effects, or the confirm-flag mechanics, even though an output schema exists so return values need no explanation. For a drop tool, that leaves meaningful behavioral gaps.

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%, with quoting guidance already provided for database, schema_name, and stream_name. The one undocumented parameter is 'confirm' (boolean, default false), and 'Requires confirmation' only loosely implies that confirm=true must be passed. Baseline 3 applies since the schema does most of the work.

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'), which is unambiguous and clearly distinguishable from siblings streams_create_stream, streams_list_streams, streams_describe_stream, and streams_read_stream_changes. It does not explicitly name an alternative or scope, but the purpose is not in doubt.

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?

Only 'Requires confirmation' is offered as guidance, which hints at the confirm flag rather than explaining when to use this tool. There is no mention of preconditions (e.g., checking the stream exists), no warning that the operation is irreversible, and no pointer to a safe alternative such as streams_describe_stream before dropping.

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