delete_stream

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

The description fails to disclose important behavioral traits like irreversibility, permissions required, or cascading effects (e.g., on dependent objects). With no annotations provided, the description carries full burden for transparency, and it does not meet that burden.

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 concise and front-loaded, consisting of a single sentence that immediately conveys the action and object. However, it sacrifices completeness for brevity.

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 simplicity of the tool (one required parameter) and the presence of an output schema, the description is still incomplete. It omits critical context such as whether deletion is permanent, whether the stream must be stopped first, and what successful deletion entails.

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 only parameter, 'stream_name', has no description in the schema (0% coverage) and the tool description adds no additional meaning. The schema's title and type are minimal, so the description fails to clarify the expected format, constraints, or examples.

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 clearly states the action ('Delete') and the resource ('a SQL stream'), which is specific and distinguishes it from siblings like 'stop_stream' or 'update_stream'. However, it could be more precise about what constitutes a 'SQL stream' versus other stream types.

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?

There is no guidance on when to use this tool versus alternatives such as 'stop_stream' or 'update_stream'. The description does not mention prerequisites (e.g., stream must be stopped) or conditions under which deletion is appropriate.

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