get_skin_temperature

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

No annotations provided. Description adds minimal behavioral info beyond purpose, such as what happens with missing data or privacy implications. With no annotations, description carries full burden but only mentions data source and recovery insights.

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 short sentences, no redundancy, front-loaded with key information. Every sentence 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?

Adequately describes purpose for a simple read tool with minimal parameters. Lacks output schema specification (no info on return format or fields), but overall context is sufficient given tool 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?

Schema coverage is 100% with descriptions for both optional 'from' and 'to' parameters. Description does not add further meaning or format details; baseline of 3 is appropriate.

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?

Clearly states verb 'Get', resource 'skin temperature data', source 'Elixir biosensing', and context 'during sleep for recovery insights'. Distinguishes from sibling tools like get_body_temperature by specifying sleep-specific measurement.

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?

Implies usage for sleep skin temperature, but no explicit when-to-use or when-not-to-use guidance. No mention of alternatives like get_body_temperature or when to prefer this tool.

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