streamlabs_remove_scene

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It explicitly states 'Permanently delete,' which communicates irreversibility—a critical trait. However, it omits potential side effects (e.g., whether sources attached to the scene are also deleted) and does not discuss error behavior or permissions.

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 a single concise sentence, front-loaded with the action 'Permanently delete.' It is free of redundancy and captures the core purpose efficiently.

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?

For a simple delete operation with one parameter and no output schema, the description adequately covers purpose, parameter, and the critical permanence aspect. It does not specify return values or error handling, but these are less critical for a destructive action where the schema and tool nature are straightforward.

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 one parameter (sceneId) with no description, and schema coverage is 0%. The description adds 'by id,' which clarifies that the parameter is the scene identifier but does not elaborate on the format, source, or how to obtain it. This is a minimal but not thorough compensation for the lack of schema documentation.

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 'Permanently delete a scene by id' clearly states the action (delete), the target (scene), and the scope (by id). It distinguishes from sibling tools like list_scenes, get_scene, and create_scene by indicating it is a destructive removal operation.

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 implies usage for deleting a scene but provides no explicit guidance on when to use this versus alternatives, no prerequisites, and no mention of when not to use it. The sibling names help contextualize, but the description itself offers only implicit usage direction.

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