openclaw_cron_add_weekly

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

No annotations provided, so description must fully convey behavior. It describes the synthesis of schedule and payload, and the call to cron.add, but does not disclose return behavior, side effects, auth requirements, or what happens if channel is omitted. Partial transparency.

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: first states purpose and mechanism, second lists parameters. No extraneous information, front-loaded with key details. Very concise 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, so description should mention return behavior; it does not. With 13 parameters, the description focuses on the core ones but omits model, agentId, instance, deliveryMode, timeoutSeconds. Schema covers them, but the lack of return info and some parameter context makes it moderately 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?

Schema coverage is 100%, so baseline is 3. The description adds value by grouping key parameters and explaining their roles (e.g., 'Pass dayOfWeek, hour, minute, tz, and message') and the optional channel delivery pair, beyond the schema's individual descriptions.

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 weekly cron job at a fixed local time, specifying the schedule and payload synthesis. It distinguishes from siblings like openclaw_cron_add_daily and openclaw_cron_add_once through the name and parameter 'dayOfWeek'.

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 lists required parameters (dayOfWeek, hour, minute, tz, message) and optional channel delivery, implying usage for weekly tasks. However, no explicit guidance on when to use this vs. other cron add tools or 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.