openclaw_talk_mode

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

No annotations provided, so description carries full burden. Discloses it is a setter (mutation) and the required boolean. However, does not discuss side effects, error conditions, idempotency, or permissions. For a mutation tool with zero annotations, more behavioral context is expected.

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 sentences, front-loaded with purpose, includes essential technical details and sibling reference. No redundant words. Efficient and well-structured.

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 exists, but description does not explain the return value or response format. Mentions wire format but not what the tool returns on success/failure. For a setter with no output schema, the agent needs to know what to expect. Missing return value documentation.

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 100%. Description adds value beyond schema: for 'enabled', it reinforces that it's a setter and required boolean; for 'instance', it provides detailed usage instructions and fallback behavior, which is not in the schema. Adds significant meaning.

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?

Clearly states 'Toggle talk mode on/off' with specific verb 'Toggle' and resource 'talk mode'. Emphasizes it's a setter, not a getter, and explicitly distinguishes from sibling tool openclaw_talk_config for reading.

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?

Provides clear guidance: use this to set state, use openclaw_talk_config to read. Mentions wire format and required boolean. Lacks explicit 'when not to use' but the distinction from the config tool is strong. Also documents optional instance parameter and fallback behavior.

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