delete_conversation_file

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

The description labels the tool as a mutation and requires confirmation to execute, disclosing its destructive nature. However, annotations are absent, so the description carries the full burden. It lacks details on permissions, side effects, or what happens after deletion.

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 very short (two clauses) and front-loaded with the action and resource. It is concise but slightly incomplete due to missing usage guidance.

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?

No output schema exists, and the description does not explain return values or confirm success. It warns about confirmation but omits other behavioral details. For a simple tool with 3 params, the description is minimally acceptable but not comprehensive.

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?

All three parameters have descriptions in the schema (100% coverage). The description does not add additional meaning beyond the schema, so baseline 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 clearly states the action (eliminar) and resource (archivo de conversacion). It distinguishes from siblings by specifying 'conversacion', though it doesn't explicitly contrast with similar deletion tools. The [mutation] tag further clarifies the nature.

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 explicit guidance on when to use this tool versus alternatives like 'delete_conversation_message' or 'delete_docqa_file'. The confirmation requirement is mentioned but not framed as a usage condition.

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