monitor_temperatures

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only 'Sensor temperature readings' and provides no details about what sensors are included, whether readings are current or continuous, or what units are returned. It adds minimal behavioral context beyond the annotations.

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 extremely brief—a noun phrase rather than a complete sentence. While there is no fluff, the brevity reflects under-specification rather than effective conciseness, and key behavioral information is missing.

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?

Given the many sibling monitoring tools and the absence of an output schema, the description is too incomplete to fully inform an agent about what will happen when invoked. It does not clarify which temperatures are covered, what the output looks like, or when this tool is appropriate.

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 tool has zero parameters, so the schema already covers everything. Description adds no parameter semantics, but none are needed; the baseline of 4 for a zero-parameter tool applies.

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 'Sensor temperature readings.' identifies the resource (sensor temperatures) and implies a read operation, but uses no explicit verb. It is not tautological, but it is too skeletal to fully distinguish behavior from other monitor_* tools without relying on the name.

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?

There is no guidance about when to use this tool versus alternatives such as monitor_cpu, monitor_gpu, or monitor_battery_health. The sibling list contains many similar monitor_* tools, and the description does not explain what distinguishes temperature monitoring from them.

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