streamlabs_push_notification

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action without mentioning side effects, permissions, whether the notification will appear in the panel, or any state changes. The description adds minimal behavioral context beyond the tool name.

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, focused sentence with zero filler. Every word contributes to stating the tool's action and target, achieving high conciseness without sacrificing clarity.

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?

The tool is simple, but the description omits contextual details that would help an agent, such as whether the notification appears in the Streamlabs Desktop notifications panel or how it relates to sibling notification tools. It is minimally viable but not fully complete given the absence of annotations and output schema.

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?

Schema description coverage is 0%, and the description is completely silent about parameters. It does not explain the meaning of 'message' or 'type', nor how the enum values (INFO/SUCCESS/WARNING) affect the notification. The schema provides the only parameter details, and the description adds no compensatory 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 uses a specific verb ('push') and resource ('new in-app notification in Streamlabs Desktop'), clearly distinguishing it from sibling tools like streamlabs_list_notifications or streamlabs_mark_notification_read. It is unambiguous and directly states the tool's purpose.

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 the notification management alternatives. It does not mention any conditions, prerequisites, or exclusion criteria, leaving the agent to infer usage from the tool name and schema.

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