openclaw_wake

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action and that it wraps a root-level method, but fails to mention side effects, state changes, idempotency, prerequisites (e.g., session must be idle), or any potential errors. This is insufficient for a mutation operation.

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 very short (three sentences) and front-loads the key action. It is efficient in word count, though it lacks depth. It could be improved without much lengthening, but for conciseness it scores well.

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 complexity of the tool (waking an agent/session from idle) and the absence of an output schema, the description is incomplete. It does not explain what the tool returns, error conditions, or prerequisites (e.g., the session must exist and be idle). Essential context is missing.

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 only 33% (only instance has a description). The description says 'Pass agentId/sessionId' but does not clarify the distinction between the two parameters, when each is required, or how they interact. It adds no meaning beyond the parameter names for agentId and sessionId.

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's action ('Wake an agent / session out of idle'), specifying the verb and resource. It uniquely identifies its role among a large set of sibling tools, as no other tool explicitly targets waking an idle session or agent.

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 provides minimal usage guidance, only instructing to 'Pass agentId/sessionId'. It does not specify when to use this tool versus alternatives, such as when an agent should be woken vs. created or reset. No explicit when/when-not conditions are given.

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