delete_synthesis_chat

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It prominently warns 'DESTRUCTIVE,' states that the full conversation history will be permanently lost, and explains the confirmation step to protect against accidental deletion. It doesn't mention return values or permissions, but given the simplicity and output schema, this is adequate.

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 opens with a clear warning, states the action, then provides a direct workflow instruction and a parameter line. There are no unnecessary words; the quoted confirmation prompt is a useful concrete detail. The structure front-loads the most critical information.

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 is a simple single-parameter delete operation. The description covers the destructive nature, the required two-step confirmation process, and the parameter identifier. Given that an output schema exists, returning value details aren't needed. The description is fully sufficient for an agent to safely invoke this tool.

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 schema only defines chat_id as a required string with no further description. The description adds 'The unique identifier of the chat to delete,' which clarifies the parameter's role but doesn't provide additional formatting or source details. With 0% schema coverage, the description only partially compensates; the one-line summary is minimal but adequate.

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 tool deletes a Synthesis Studio chat and its entire message history, using the specific verb 'delete' and identifying the resource. This distinguishes it from sibling tools like create_synthesis_chat, get_synthesis_chat, and send_synthesis_message.

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?

It explicitly instructs not to call the tool in the same turn as the deletion request and to first ask for user confirmation, then only call after a follow-up confirmation. While it doesn't name alternative tools, the when/when-not guidance is explicit and actionable for a destructive operation.

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