get_hydrometer_telemetry

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns timestamped readings and is historical in nature, but it doesn't mention behavior such as default date ranges, potential pagination, or explicitly confirm it's a read-only operation (though 'Get' strongly implies this). Given the lack of annotations, a bit more behavioral context would be beneficial.

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, well-structured sentence that front-loads the core purpose ('Get historical telemetry data') and then adds specific return content. Every word earns its place, with no wasted or redundant phrasing.

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 straightforward read-only telemetry tool, the description and schema together provide a solid picture. The lack of an output schema is mitigated by the explicit mention of gravity, temperature, and battery readings. However, it would be more complete if it noted behavior like what happens when no dates are supplied or how the profile_session_id filter works, but these are minor gaps given the tool's simplicity.

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 input schema already describes all parameters with 100% coverage, so the baseline is 3. The description does not add extra meaning to the parameters (e.g., how start_date/end_date interact, or what profile_session_id filters by), but it also doesn't need to since the schema descriptions are adequate.

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 specifies the action ('Get historical telemetry data'), the target resource ('a RaptPill hydrometer'), and the exact data returned ('timestamped gravity, temperature, and battery readings'). This distinguishes it from sibling tools like get_hydrometer (likely current state) and get_fermentation_chamber_telemetry, 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 description clearly implies when to use this tool: whenever historical telemetry from a hydrometer is needed. It doesn't explicitly contrast with alternatives (e.g., 'use this instead of get_hydrometer for historical data'), but the context is clear enough that an agent can infer its role relative to sibling tools.

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