Trigger a verified Stream Deck action

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'emit' without explaining that actions like live-pause or stop_live have immediate side effects on the streaming session. It also omits prerequisites (e.g., must be live) or whether the action is reversible.

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?

Two sentences: one for purpose, one for usage boundary. No wasted words.

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 trigger with a single enum parameter and no output schema, the description gives the core purpose and a usage constraint. However, it lacks explicit mention of real-world effects (e.g., pausing live will affect the broadcast), though the enum names imply this.

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 already fully describes the single parameter with an enum and descriptions (100% coverage). The description adds no parameter-specific meaning beyond hinting that non-parameterized actions are appropriate here.

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 title and description clearly state the tool emits a verified Stream Deck action. The phrase 'Emit one action from the verified LIVE Studio 1.33.2 Stream Deck protocol' specifies the verb and resource, and the sibling tools (status, scenes, sources, recording/live controls) make this distinct.

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 explicitly states 'Parameterized and stateful actions should use dedicated tools,' giving a when-not condition. However, it does not name specific alternative tools, so it falls just short of an explicit alternative list.

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