heater_shaker

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

No annotations provided, so description carries full burden. It lists actions but omits behavioral details like whether deactivate turns off heating or what status returns. Adequate but minimal insight into side effects.

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?

Extremely concise: one sentence with purpose then bullet-like action list. Every word is informative, no redundancy. Front-loaded with core purpose.

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?

For a simple device control tool with 4 parameters (1 required) and no output schema, the description covers essential use cases. It could be more complete by explaining return values or differences between stop and deactivate, but overall sufficient.

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 lacks descriptions (0% coverage). The description compensates by explaining the action parameter values and clarifying units (Celsius, rpm, seconds) for relevant parameters, adding value beyond schema.

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 controls the heater-shaker and enumerates specific actions (set_temperature, shake, stop, deactivate, status), distinguishing it from sibling tools which are all different lab operations.

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 explains when to use each action and what parameters are needed (e.g., set_temperature requires temperature in Celsius). However, it does not explicitly state conditions for not using the tool or mention alternatives, though siblings are distinct.

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