openclaw_cron_add_once

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

With no annotations, the description carries the full burden. It correctly states the job fires once then auto-deletes, but omits edge cases like past timestamps or name uniqueness requirements.

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?

Three sentences, front-loaded with the core purpose, then technical detail and parameter hint. No redundant or extraneous text.

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 scheduling tool with 10 parameters and no output schema or annotations, the description covers the essential behavior but misses guidance on timestamp validation, name uniqueness, and optional channel setup.

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 90%, so the description adds little beyond what the schema provides. It repeats the RFC3339 format for 'at' and mentions 'message', but does not explain optional parameters like 'channel' or 'deliveryMode'.

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 it creates a one-shot reminder/job that fires once and auto-deletes. It specifies the schedule type and required parameters, distinguishing it from recurring cron tools like openclaw_cron_add.

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 implies usage for one-shot jobs by naming it 'add_once' and describing the auto-delete behavior. However, it does not explicitly contrast with recurring variants or mention when not to use it.

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