sensor_stream

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

Annotations are all false, so the description carries the full burden of behavioral disclosure, yet it only says the series is bounded. It does not state whether the call blocks, how termination is determined, whether it starts a background stream, or what side effects (if any) occur.

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 a single compact sentence with no filler and the main action is front-loaded. It is efficiently written, though it is so minimal that it sacrifices useful explanatory content.

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?

With 5 parameters, no output schema, and no annotation support, the description omits essential context such as termination conditions, sample rate/count semantics, return structure, and how this tool differs from sibling sensor tools. An agent cannot reliably predict the behavior or result of a call.

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 adds no parameter-level meaning. It does not explain how max_samples, duration_seconds, and sample_interval_ms interact, nor does it clarify valid port/sensor_type combinations beyond the raw enums.

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 uses a specific verb ('Collect') and resource ('sensor readings') with the qualifier 'bounded series,' which conveys the core function of gathering multiple samples. It is distinguishable from single-reading siblings like read_sensor, but it does not explicitly name or contrast them.

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 guidance about when to use sensor_stream versus read_sensor, read_sensor_raw, wait_sensor, or log_start. The phrase 'bounded series' implies multi-sample collection, but no explicit when/when-not conditions or alternative routing is provided.

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