schedule_task

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

Without annotations, description covers daemon persistence and result storage. But it lacks details on permissions, resource implications, or side effects of scheduling autonomous tasks. Adequate but not comprehensive.

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?

Five sentences efficiently convey core purpose, behavior, and examples. No redundancy. Slight room for improvement by front-loading the most critical information, but overall 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?

With 10 parameters and no output schema, the description covers main functionality but omits return value (e.g., schedule ID) and does not explain 'delayed one-shot' fully. Some advanced parameters like catchup, serviceTier, reasoningEffort are not addressed.

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 covers all parameters (100% coverage), so baseline is 3. Description adds value with cron format guidance, provider defaults, and some mapping details (e.g., model to service_tier).

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?

Description clearly states the verb 'schedule', resource 'CLI agent', and schedule type 'cron or delayed one-shot'. It also specifies the default provider, distinguishing it from siblings like cancel_schedule and get_scheduled_results.

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?

Description explains when to use the tool (to schedule tasks) and provides cron format examples. However, it does not explicitly state when not to use it or suggest alternatives, though the context of siblings is informative.

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