streamlabs_delete_scene_collection

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

With no annotations, the description carries the full burden. It explicitly states 'it is destructive' and 'Confirm with the user before calling this', disclosing the destructive nature and required safety step. It also reveals the default behavior when no id is given. This is solid, though it could add more (e.g., irreversibility details or error handling), but it exceeds the minimum.

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 sentences, front-loaded with the action, and every word earns its place. It avoids redundancy and is efficiently structured.

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 simple single-parameter destructive tool with no output schema. The description covers the essential aspects: what it does, parameter behavior, and safety confirmation. It is complete enough for an agent to select and invoke correctly without additional context.

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 only provides a type string with no description, and coverage is 0%. The description compensates fully by explaining that the id refers to the scene collection, and if omitted, the active one is deleted. This precisely clarifies the optional parameter's meaning and default behavior, adding significant semantic value.

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 scene collection by id', using a specific verb and resource, and distinguishes from siblings like create, rename, load, and list. It also adds the nuance of deleting the active collection if no id is given, making the purpose unambiguous.

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 clear context: use this to delete a scene collection, either by id or the active one if id omitted. It also instructs to confirm with the user because it is destructive, which is a key usage guideline. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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