delete_chat

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

Annotations already declare destructiveHint=true. The description adds 'This is irreversible' which reinforces the destructive nature. However, no additional behavioral traits (e.g., effects on participants, message deletion) are disclosed, so the description adds only modest value beyond annotations.

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 brief and front-loaded with the main purpose, followed by an Args section. It contains no unnecessary text. Slightly more structured formatting could be beneficial, but it remains concise.

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 tool's simplicity (one parameter, destructive, with output schema present), the description adequately covers the purpose, irreversibility, and parameter meaning. However, it could mention that the chat must exist or what happens to associated data, but overall it is sufficient.

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 compensates by explaining chat_guid as 'The chat GUID to delete'. This provides essential meaning for the single parameter, making up for the lack of schema descriptions.

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 'Delete an entire chat conversation' with the resource 'chat conversation'. It also notes irreversibility. This distinguishes it from sibling tools like remove_participant (removes a person) and leave_chat (exits chat without deletion).

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 guidance on when to use this tool versus alternatives like leave_chat or remove_participant. The description does not mention prerequisites, required permissions, or comparison with similar tools.

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