Api chat sessions destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of permanence, cascading effects on messages/documents, or auth requirements — and its 'streaming message endpoint' framing pulls in the opposite direction from a delete.

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?

It is short, but the single sentence is boilerplate that does not earn its place: for a destructive operation it is under-specified rather than concise. Length is fine; content is misplaced.

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?

A destructive mutation with no output schema, an undocumented required parameter, and no annotation beyond hints. The description supplies none of the missing information an agent needs to call it safely.

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 must carry the burden for the single required 'id' parameter, and it does not. It never clarifies whether id is the session UUID, whether it must exist, or what happens if it does not.

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 is a class-level docstring ('ViewSet for chat sessions with streaming message endpoint') that names the resource but never states the action. It reads like a browsing/streaming tool, while the tool name and annotations indicate permanent deletion of a single session. An agent reading only the description would not know this removes a chat 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?

No guidance on when to delete a session versus using the many sibling tools (chat_sessions_list, chat_sessions_retrieve, chat_sessions_partial_update, chat_sessions_batch_action_create). No prerequisites, no warnings about irreversibility, no indication of what the id refers to.

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