drone_streaming

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

No annotations are provided, so the description carries the behavioral burden. It states that the tool supports multiple protocols, real-time monitoring, quality adaptation, and conversational status updates. However, it stays high-level and does not cover stateful prerequisites or side effects such as stopping an active stream or recording.

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 short but repetitive: conversational responses and conversational status updates say essentially the same thing, and the third sentence largely restates the second. Vague phrasing such as intelligent quality adaptation adds little concrete value.

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 input schema and output schema reduce some burden, but for a seven-operation tool with no annotations, the description still lacks workflow prerequisites such as requiring an active stream for get_stream_url, requiring a filename for recording, and how this tool relates to the other drone tools.

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 100%, so each parameter is already documented. The description adds only broad protocol and quality context, not operation-specific parameter constraints, so it remains at the baseline expected for a well-covered 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 identifies a concrete resource: drone video streaming and recording, including FPV feeds, RTSP/WebRTC streaming, and onboard recording. It is specific enough for an agent to recognize this as a streaming/capture tool, though it does not explicitly contrast it with sibling tools like drone_control.

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?

There is no explicit when-to-use or when-not-to-use guidance. With many sibling drone-related tools, the description does not tell an agent which situations select drone_streaming over drone_control or drone_flight_control.

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