openclaw_node_pending_enqueue

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Mutates' but does not explain the nature of the mutation (e.g., async queuing, side effects, response format, or whether the enqueue is guaranteed). The agent lacks critical behavioral detail for safe invocation.

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 brief: two sentences that directly state purpose and mention the wrapped function. It is front-loaded and avoids fluff. However, it is perhaps too minimal; a bit more detail could be added without harming conciseness.

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 no output schema, 2 params (one undocumented), and no annotations, the description should provide more context. It does not explain return values, error states (e.g., unknown nodeId, queue full), or the effect of the 'additionalProperties' allowed in the schema. The tool's behavior is only partially described, leaving significant gaps.

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 50% (only 'instance' has a description). The description adds no new meaning for 'nodeId' beyond what the schema provides (just minLength:1). For 'instance', the schema already describes routing; the description does not elaborate. With low coverage and no added semantics, the agent may not understand the required input for nodeId.

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 'Enqueue a new work item for a node' with a specific verb and resource. The mention of wrapping `node.pending.enqueue` further clarifies the internal function. Among siblings like openclaw_node_pending_pull, drain, ack, this tool is distinctly for enqueuing, so purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives such as openclaw_node_invoke or other pending operations. There is no mention of prerequisites (e.g., node must be paired or active) or conditions for using enqueue over other tools. The agent is left to infer usage context from the tool name alone.

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