measurements_list_temperature

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that temperature readings are listed and does not mention pagination limits, ordering defaults, filtering semantics, or the read-only nature beyond what the name implies.

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, front-loaded sentence with no filler or redundant phrasing. It is efficiently minimal, though it leaves most contextual information to the schema.

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 7 optional parameters, no annotations, and many sibling measurement tools, this sparse description does not give the agent enough orientation. It omits mention of date filtering, tags, child scoping, ordering, and default limits, and offers no usage guidance; the output schema may cover return values, but not selection context.

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 100% and all 7 parameters are well-documented in the schema, so the baseline is 3. The description itself adds no parameter semantics, but the schema fully compensates for that gap.

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 ('List') and resource ('temperature readings'), clearly identifying this as a read-only listing operation for temperature measurements. It is distinguishable from sibling measurement list tools by the resource type, though it does not explicitly contrast with measurements_list_bmi, measurements_list_height, etc.

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 given on when to use this tool versus sibling list tools or the create/update/delete temperature tools. There is no mention of supported use cases, default behavior, or how the filter parameters should be applied; the agent must infer all of this from the name and schema.

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