get_sensor_data

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

The description discloses a specific non-obvious behavior: sensor queries use blocking serial I/O and 'may block the event loop briefly'. With no annotations to rely on, this adds valuable context about performance impact and safety of calling this tool in time-sensitive situations.

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 two short sentences with no filler. It front-loads the purpose and adds one key behavioral note, every word earning its 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?

Despite having an output schema, the tool description leaves critical gaps: the 'sensors' parameter is unexplained, and there is no context on how this relates to streaming APIs or which sensor identifiers to use. The blocking warning is useful but insufficient to make the tool self-contained.

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 0% description coverage, and the description does not mention the 'sensors' parameter at all. The parameter is an array of untyped items with a default of null, leaving the agent guessing what strings or objects to pass. The description must compensate for this ambiguity but completely fails to do so.

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 'Get sensor data' clearly identifies a getter operation on sensor resources. However, it does not differentiate this tool from several sibling tools such as get_ambient_light, get_temperature, or start_sensor_streaming, so it lacks sibling differentiation.

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 about when to use this tool versus alternatives like start_sensor_streaming or specific sensor getters. The only additional note is a behavioral warning about blocking I/O, which is not usage guidance.

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