Delete Jules Session

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

The annotations already provide destructiveHint and idempotentHint, but the description augments this with 'This action cannot be undone,' which emphasizes irreversibility. It also forecasts the return value ('Confirmation of deletion'), adding behavioral insight beyond the structured metadata. No contradiction exists between the description and annotations.

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 brief and front-loaded with the purpose statement, then organized into Args/Returns/Note sections. Each line has a purpose, and the irreversibility note is placed at the end for emphasis without wasting words.

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 single-parameter delete operation with full annotations, the description covers the essential aspects: what it does, what it takes, what it returns, and its irreversibility. It doesn't explore edge cases or side effects, but the openWorldHint annotation suggests unspecified external effects, and the description's simplicity matches the tool's low complexity.

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?

The schema already provides 100% description coverage for the sessionId parameter with the same wording ('The session ID to delete'). The description's Args section repeats this without adding detail about ID format, acquisition, or constraints beyond the schema, so it meets the baseline but provides no extra semantic value.

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 opens with 'Delete a coding session,' using a specific verb and resource that clearly distinguishes it from sibling tools like jules_get_session and jules_create_session. The irreversibility note reinforces that this is the deletion action, eliminating ambiguity.

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 the tool's use case (when you need to permanently delete a session) but does not explicitly state when to use it versus alternatives. There is no mention of conditions such as 'use this instead of archiving' or 'do not use if session is still needed,' so the guidance is implicit rather than explicit.

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