Get thermal status

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

Description fully discloses the tool is a read operation and details the output data. No annotations provided, so description carries full burden; it is transparent about behavior and does not contradict any implicit assumptions.

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 well-structured sentences, front-loaded with purpose and output details. Every sentence adds value; no fluff.

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?

No output schema, but description comprehensively lists return fields. Parameter count is zero, so complexity is low. Description covers all necessary context for a read-only monitoring tool.

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?

No parameters in the input schema, so baseline score of 4 applies. Description doesn't need to add parameter information; it is appropriately concise on this dimension.

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?

Title and description clearly state it reads the thermal state, listing specific data points (sensor temps, fan RPM, power draw, fan-control state). Distinguishes from sibling tools like boost_fans and set_fan_auto by being a read-only status tool.

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?

Explicitly states when to use the tool: 'before and after changing fan speeds, or to decide whether pre-cooling is worthwhile.' Provides clear context but lacks explicit when-not-to-use scenarios.

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