reachy_wake_up

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It merely restates the concept of waking up and provides no detail about physical movement, duration, blocking behavior, side effects, or failure conditions.

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 a single compact sentence with the key verb front-loaded. The phrase 'execute wake up behavior' is slightly redundant, but the overall size is appropriate.

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 zero-parameter command, this is minimally viable: the agent knows what the tool does. However, with no output schema and no annotations, the description leaves out expected side effects and operational context, so it is not fully complete.

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?

There are zero parameters and an empty required list, with schema coverage at 100%. No parameter documentation is needed, so the description does not need to compensate for missing parameter semantics.

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 uses a specific verb ('Wake up') and a clear resource ('the robot'), making the tool's action unmistakable. It does not explicitly distinguish itself from siblings, though it is logically the opposite of reachy_go_to_sleep.

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 call this tool, what conditions should hold first, or how it compares to alternatives such as reachy_go_to_sleep or reachy_reconnect. The only implied usage is that waking up precedes robot interaction, but this is left to inference.

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