jules_list_sessions

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

With no annotations, the description must disclose behavioral traits. 'List' implies read-only and 'authenticated account' indicates scoping, but it does not explain pagination behavior, ordering, or whether any side effects occur. Minimal transparency beyond the action itself.

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, efficient sentence placed at the start. No filler or redundant phrasing—every word contributes to the tool's purpose.

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?

The description is adequate for a straightforward list operation with an output schema present. However, it lacks guidance on pagination semantics, alternative selection, and any authentication prerequisites, so an agent would need to infer some context.

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 0%, so the description should compensate for the two parameters (page_size, page_token). It does not mention them or pagination at all. Parameter names and defaults in the schema provide some meaning, but the description adds none.

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 uses a specific verb ('List'), a clear resource ('Jules coding sessions'), and a scope ('for the authenticated account'). It distinguishes itself from siblings like jules_list_sources and jules_get_session by specifying the exact object being listed.

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 usage context is implied: use this to retrieve all sessions for the authenticated user, as opposed to getting one session (jules_get_session) or listing other entities (jules_list_sources, jules_list_activities). However, no explicit alternatives or when-not-to-use conditions are given.

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