get_sensor_readings

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

With no annotations, the description carries the full burden. It discloses the time window ('latest ~24 hours') and data format, but does not mention ordering, units, error behavior, or rate limits. This is more than a tautology but still sparse.

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?

Two concise sentences with the key purpose first, then format and time range. No filler or redundant phrasing. Every word adds 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?

For a simple tool with one parameter and no output schema, the description conveys the core behavior (what it returns and the time scope). It does not cover details like sorting order or pagination, but these may be implicit in a simple read operation. Minor gaps remain, but it is adequate.

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 already describes sensor_id well with 100% coverage, including its source ('from get_station_sensors'). The description adds no extra parameter-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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 states a clear verb ('Get'), a specific resource ('recent measurement readings from a sensor'), and the data format ('(measured_at, value) pair'). It distinguishes from siblings like get_air_index (which implies an index, not raw readings) and get_station_sensors (which likely lists sensors, not readings).

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 description mentions that sensor_id comes from get_station_sensors, implying a prerequisite call, but does not explicitly state when to use this tool versus alternatives (e.g., get_air_index). No exclusions or conditions are provided.

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