acp_create_scheduled_session

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

No annotations are provided, so the description carries full behavioral burden. It discloses the CronJob backend, but lacks details on failure handling, resource creation, default suspend behavior, or permissions required. The `suspend` parameter (with default false) is not mentioned in the description.

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, second states prerequisites. No extraneous words. Front-loaded and efficient.

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 or annotations, the description should compensate with return value or error handling information, but it does not. The schema covers parameter details, but the description omits defaults (suspend, dry_run) and any post-creation behavior, making it only partially complete for a creation tool with nested objects.

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 the baseline is 3. The description adds marginal value by stating 'Requires a cron schedule and a session template' and referencing `create_session` for the template structure, which aids understanding. This slight addition justifies a 4.

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 the tool creates a scheduled session backed by a Kubernetes CronJob, requiring a cron schedule and session template. It differentiates from siblings like `acp_create_session` (non-scheduled) and `acp_trigger_scheduled_session` (immediate execution) by specifying scheduling behavior.

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 mentions prerequisites (cron schedule and session template) but does not guide when to use this tool versus alternatives such as `acp_create_session` for one-off sessions or `acp_update_scheduled_session` for modifying existing schedules. No explicit context on 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.