jules_delete_session

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

With no annotations, the description carries the burden of behavioral disclosure. It does state the operation is permanent and spans accounts, which conveys irreversibility and scope. It does not mention permissions, side effects on related data, or whether the action can be undone beyond the word 'permanently', so it is only moderately transparent.

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?

The description is a single, tightly-worded sentence that conveys the essential action, scope, and irreversibility without any filler or repetition of schema details.

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 simple one-parameter destructive tool, the description covers the key aspects: what is deleted, permanence, and cross-account scope. Minor gaps such as authentication requirements or effects on dependent resources remain, but they do not critically impair an agent's ability to call it correctly.

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 100% and the only parameter, session_id, is described as 'The session ID.' The description adds no further meaning about how to obtain or format the session ID, so the baseline of 3 applies.

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 clear verb ('delete'), a specific resource ('session from Google Jules'), and adds distinguishing scope ('across accounts') and permanence ('permanently'). This clearly differentiates it from related tools like jules_archive_session.

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 implies usage: use this when you want a permanent, cross-account session deletion. However, it does not explicitly state when to avoid this tool or mention that archive_session is the non-destructive alternative, leaving the choice partially to inference.

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