start_sensor_streaming

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 only says 'Start sensor streaming' without mentioning whether this blocks, how streaming is delivered, or if it requires an active connection. This is a significant omission for a state-changing operation.

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?

While the description is short, it sacrifices meaningful content for brevity. It reads more like an under-specified label than a helpful tool description.

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?

Given the tool's two parameters, existence of an output schema, and lack of annotations, this description is grossly insufficient. It provides no details on return values, sensor data format, streaming lifecycle, or interval semantics, making it hard for an agent to use correctly.

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 mention either parameter. The required 'sensors' array and optional 'interval_ms' are entirely unexplained, leaving the agent to guess their format and effect.

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 clear verb 'start' and resource 'sensor streaming', which identifies the action. However, it lacks specificity about what 'sensor streaming' means or how it differs from related tools like get_sensor_data. It is not tautological but is vague.

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?

No guidance is provided for when to use this tool versus alternatives such as stop_sensor_streaming or get_sensor_data. The description does not mention prerequisites, intended scenarios, or exclusions.

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