Delete a session

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

The description adds nothing beyond the annotations: destructiveHint=true and idempotentHint=true already communicate the core safety profile. It does not disclose whether deletion is permanent, whether it can be undone, or any side effects on related data.

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 tight sentence with no filler or repetition of schema content. It is appropriately front-loaded and concise, though it could also include a brief behavioral warning without becoming bloated.

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 one-parameter delete operation, the schema and annotations carry most of the burden: the parameter is documented and the destructive/idempotent behavior is annotated. However, the lack of any statement about permanence or how delete compares to archive leaves an important gap for an agent deciding whether deletion or archiving is intended.

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 fully describes the single parameter session_id as 'The Jules session ID', so the description does not need to compensate. It also adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.

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 the specific verb 'Delete' with the explicit resource 'Jules session', making the operation unmistakable relative to sibling tools like get/list/create. It clearly states what the tool does in one unambiguous phrase.

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 gives no guidance on when to use delete versus alternatives such as archive_session or unarchive_session. There are no when-to-use conditions, prerequisites, or warnings about preferring archive over deletion.

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