delete_library_streams_by_stream_id_ext

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

The description adds no behavioral context beyond what annotations already declare (destructiveHint=true, idempotentHint=true, readOnlyHint=false). It does not describe irreversible effects, whether deletion is permanent, or any special handling. The note about ext being a placeholder is about parameter semantics, not tool behavior.

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 structured with an endpoint line and Args section. It front-loads the action 'Delete a stream.' and avoids unnecessary verbosity, but the inclusion of the ext note adds minor clutter.

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 this is a destructive operation with annotations indicating destructiveness, the description is incomplete. It does not explain the impact of deleting a stream (e.g., whether it is permanent, what dependencies exist), nor does it provide usage context. The ext parameter is clarified, but the overall context for an agent to confidently invoke this tool is insufficient.

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 schema has no parameter descriptions (0% coverage), so the description compensates by explaining stream_id as 'the id of the stream' and clarifying that ext is 'not a part of this endpoint but documented here to satisfy OpenAPI.' This is helpful, but the stream_id explanation is trivial and no additional context about how to obtain the ID is given.

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 'Delete a stream' and shows the endpoint path, giving a specific verb and resource. It distinguishes from siblings like get_library_streams_by_stream_id_ext and update_library_streams_by_stream_id_ext by the action, but does not elaborate on what deleting a stream entails.

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 such as update_library_streams_by_stream_id_ext or get_library_streams_by_stream_id_ext. It does not mention prerequisites, conditions, or side effects that would help an agent decide to invoke deletion.

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