streamlabs_show_notifications_panel

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

No annotations are provided, so the description carries the full burden. 'Open/focus' conveys that the tool performs a non-destructive UI focus action, but it does not disclose potential side effects (e.g., whether it brings the panel to front, requires the app to be running, or fails silently if the panel is already open). This is acceptable for a simple UI action but not richly transparent.

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 sentence with only ten words. It is perfectly concise and front-loaded: the verb 'Open/focus' appears immediately, and the resource is specified clearly. No filler or redundant content.

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 tool has no parameters, no output schema, and a simple UI action, the description is largely complete. However, it could briefly mention that the Streamlabs Desktop app must be running or that the action is idempotent, which would make it more robust. Still, for this complexity level, it suffices.

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 tool takes zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and indeed the schema is empty. The description adds no parameter information, which is fine given there are none.

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 uses the specific verb 'Open/focus' and names an exact resource: 'the notifications panel in the Streamlabs Desktop UI'. This clearly distinguishes it from sibling tools like streamlabs_list_notifications or streamlabs_mark_notification_read, which operate on notification data rather than the UI panel.

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 gives no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. While the purpose is clear, the agent is left without explicit context on when this UI action is appropriate compared to the many notification-related siblings.

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