get_stream_info

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that the stream is not opened, and it describes platform-specific metadata reporting (iOS: WDA MJPEG URL/settings, screenshot fallback, unsupported Portal/WebRTC; Android: Portal/H264/screencap), which is valuable behavioral context.

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 concise and front-loaded with the core purpose. The following sentences add focused platform-specific detail without fluff or repetition, earning their place.

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?

Purpose and platform behavior are well covered, and the presence of an output schema covers return-value details. However, the absence of parameter semantics and explicit usage guidance leaves gaps that could affect correct invocation, so it is only partially complete.

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 does not explain any of the four parameters (fps, mode, device, quality). No meaning or effect of these parameters is provided, leaving the agent without sufficient information to set them correctly.

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 function with a specific verb and resource: 'Return effective stream metadata without opening the stream.' It also differentiates from sibling tools by detailing platform-specific metadata (iOS vs Android), making its purpose unambiguous.

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 phrase 'without opening the stream' implies a lightweight use case, but no explicit guidance is provided on when to choose this tool over alternatives. There are no mentions of exclusions, prerequisites, or sibling comparisons.

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