ragflow_delete_agent_sessions

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is given. The description's one added word, 'Permanently', reinforces irreversibility but adds little beyond what destructiveHint conveys, and it says nothing about whether deleting a session also removes its messages or whether the operation is batch-atomic.

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?

A single front-loaded sentence with no filler and the destructive nature stated immediately. It is efficient, though arguably terse to the point of under-specification for a permanent-delete 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?

The tool has an output schema, full parameter documentation, and annotations covering safety, so much is already structured. Still, for a permanent batch delete the description omits cascade effects, partial-failure behavior, and the distinction from sibling delete tools, leaving a moderate gap.

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 both parameters (agent_id, session_ids) are documented in-schema, so baseline 3 applies. The description adds no semantics beyond the schema — notably it doesn't clarify that session_ids accepts multiple sessions for a batch delete or what happens if some IDs are invalid.

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?

States a specific verb ('Permanently delete') and a precise resource ('conversation sessions of an agent'), which distinguishes it from the sibling ragflow_delete_chat_sessions (chat sessions) and from ragflow_list_agent_sessions. It never names the siblings explicitly, so the differentiation is inferred from the 'agent' scope rather than spelled out.

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 when-to-use guidance, no prerequisites, and no alternatives. An agent could reasonably wonder whether deleting an agent (ragflow_delete_agent) or deleting chat sessions is the right call in a given situation; nothing here helps resolve that.

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