Set stream destination

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

With no annotations, the description must carry the transparency burden. It accurately states the action ('Set') and provides an example, but does not disclose whether settings are merged or replaced, validation rules, or whether it requires OBS to be running. Not misleading, but thin.

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 one sentence plus an example, with no redundant wording. It is front-loaded and concise.

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 a simple setter with a nested object, and an output schema exists, so return values are already covered. The description provides the essential purpose and example, but could elaborate on service_type values and settings merge behavior for full completeness.

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 coverage is 0%, so the description must compensate. It mentions 'server URL, stream key, service name, etc.' and gives an example, partially clarifying the 'settings' parameter. However, the 'service_type' parameter is left unexplained, and the structure of 'settings' is still vague.

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 the tool's purpose: 'Set the stream service and its settings' and provides a concrete example. It distinguishes this from sibling tools like get_stream_service_settings (which retrieves) and start_stream (which begins streaming).

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 configuring stream destination, but does not explicitly state when to use it versus alternatives, nor any prerequisites or exclusions. The example provides some context but lacks direct guidance.

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