Api chat documents 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 externally. The description adds nothing beyond that — it does not say what deletion entails (e.g. whether the vector index entry and embeddings are removed, whether the underlying session/document record survives, or whether authorization is required).

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?

One short sentence with no padding, but the brevity comes from under-specification rather than economy: the words spent convey no actionable information about the operation.

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?

This is a destructive single-parameter tool with no output schema; the description should at minimum confirm the delete semantics and what a successful/404 response means. It supplies none of that, so an agent cannot safely call it without opening the schema and inferring intent from the name alone.

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% for the single required 'id' parameter, so the description carries the full burden and must say what identifier is expected (document UUID, integer, display ref). It says nothing, leaving the agent to guess the id's format and origin.

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 identifies the resource ('indexed documents') but never states the operation. The name and title say 'destroy', yet the text reads as a generic ViewSet docstring ('ViewSet for managing indexed documents') that could equally describe list, retrieve or update — it does not distinguish this tool from the many sibling chat_documents_* tools.

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?

There is no when-to-use guidance at all: nothing says this permanently removes an indexed chat document, nor points to alternatives such as chat_documents_update for modification or chat_documents_retrieve for inspection. The reader must infer everything from the tool name.

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