Schedule Recurring Jules Session

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

With no annotations provided, the description must carry the behavioral burden, and it only discloses durability ('persistent') and recurrence ('cron'). It does not state whether a session runs immediately upon scheduling, whether duplicate schedules are allowed or overwritten, what the default autoApprove/autoCreatePR behavior implies for future autonomous runs, or what the response contains.

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?

A single 10-word sentence with zero filler; 'persistent' and 'cron' earn their place by conveying durability and recurrence. It is efficiently front-loaded, though given the 8-parameter complexity and 19 siblings, the brevity veers toward under-specification rather than ideal 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?

For a tool with 8 parameters, no annotations, no output schema, and 13% schema coverage, one sentence is far from complete. Missing context includes the return format (does it return a schedule ID?), the relationship to jules_cancel_recurring_schedule/jules_list_recurring_schedules, and the operational consequence that scheduled sessions will run autonomously on a recurring basis.

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 description coverage is only 13% (only 'cron' has a terse description), so the description must compensate, but it mentions no parameters at all. While repoOwner/repoName/prompt are self-evident by name, autoApprove and autoCreatePR carry behavioral meaning (autonomous approval, PR creation on each run) that neither the schema nor the description clarifies.

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 states a specific action ('Create'), a specific resource ('persistent cron schedule for recurring Jules sessions'), and the scope (recurring vs one-off). This clearly separates it from one-off session tools like jules_create_session and jules_bulk_create_sessions, though it does not explicitly name a sibling as the gold-standard examples do.

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 is given on when to choose this tool over alternatives. With 19 siblings including jules_create_session, jules_bulk_create_sessions, jules_list_recurring_schedules, and jules_cancel_recurring_schedule, the absence of any routing cue ('use X for one-off sessions') leaves the agent to infer the decision criteria.

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