get_body_temperature

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool is read-only (Get) and mentions device compatibility, but does not clarify behavior on unsupported devices, data absence, rate limits, or any side effects. The minimal disclosure leaves significant gaps for an agent.

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 concise with two sentences, no redundant words. It efficiently conveys the tool's purpose and device requirement without unnecessary details.

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 no output schema and no description of return values, the agent lacks information about what data the tool returns (e.g., temperature readings, timestamps, units). The description does not compensate for missing output details, making the tool incomplete for informed invocation.

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 has 100% coverage with descriptions for both 'to' and 'from' parameters. The tool description adds no extra meaning beyond the schema, so it meets the baseline of 3. No further value is provided.

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 states the tool retrieves body temperature data from Elixir biosensing on compatible Polar devices. It specifies the resource (body temperature) and differentiates from sibling tools like 'get_skin_temperature' by naming the sensor technology and device compatibility.

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 provides no guidance on when to use this tool versus alternatives (e.g., get_skin_temperature). No prerequisites, exclusions, or context for selecting this tool are mentioned, leaving the agent without decision support.

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