conversations_delete_conversation

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

The description adds no behavioral information beyond the annotations. Annotations already indicate the tool is destructive and idempotent, but the description does not elaborate on consequences (e.g., permanent deletion) or any other side effects. With annotations present, the description could still add value by explaining what gets destroyed, but it stays silent.

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 extremely concise, consisting of two words, and is front-loaded with the action. It is not verbose or redundant, and every word serves a purpose. While minimal, it adequately conveys the operation for a simple delete tool.

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?

Given the low complexity (one parameter, no output schema) and that annotations cover destructive and idempotent behavior, the description is minimally sufficient. However, it could be more complete by mentioning that deletion is permanent or irreversible, but it does not. Overall, it is adequate but not rich.

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 input schema provides 100% coverage of the single parameter, including its type and description. The tool description adds no extra meaning to 'conversationId' beyond the schema. Per the rubric, a high schema coverage baseline of 3 applies, and the description does not exceed that.

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 states the verb 'Delete' and the resource 'Conversation', clearly indicating the action. It is unambiguous and not a tautology, but it does not differentiate from sibling tools that also delete resources in the conversations domain, such as messages or scheduled messages.

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 is provided on when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. The description simply states the action without context for an agent to decide if this is the right tool for a given scenario.

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