set_stream_service_settings

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

No annotations are provided, so the description carries the full burden. It explains how to set service_type and settings but does not disclose that this is a state-changing operation that may affect live streaming, require authentication, or behave differently for other service types. The only extra behavioral context is the example for a plain RTMP target.

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 brief and front-loaded, with the purpose in the first line. The Args section is minimal and the example is valuable, though it partially duplicates parameter names already present in the schema.

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 mutation tool with no annotations or output schema, the description provides only basic guidance. It covers the rtmp_custom case but leaves rtmp_common and other service types undefined, and lacks information about validation, potential side effects, or the expected response.

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 has no property descriptions, so the description is the sole source of parameter meaning. It explains service_type with examples and defines settings as a service-specific object. The rtmp_custom example gives concrete structure for the settings parameter, adding value beyond the bare schema.

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 'Set the stream destination' with a specific verb and resource, distinguishing it from the sibling get_stream_service_settings. The example for rtmp_custom further clarifies its 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?

It provides a concrete usage example for rtmp_custom, indicating when this setting is appropriate. However, it does not explicitly mention alternatives or when not to use it, relying on the reader to infer context from the example.

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