delete_conversation_message

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

The description discloses it is a mutation operation requiring confirmation, which is positive. However, no annotations are provided to supplement behavioral traits, and the description lacks details on irreversibility, side effects, or permissions required, leaving gaps in transparency.

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 concise with key information front-loaded: purpose, requirement, mutation tag, and confirmation needed. It could be slightly more structured but efficiently conveys the essential points.

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 description lacks information about return values or outcome of success/failure. With no output schema, the agent is left uninformed about what happens after deletion, making it incomplete for a mutation 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?

All 14 parameters have descriptions in the input schema (100% coverage), so the schema does the heavy lifting. The description re-emphasizes the exact message requirement but adds no new semantic value beyond what the schema already provides.

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 specific message from a conversation, using specific verbs and resource. It distinguishes itself from sibling delete tools by specifying 'conversation message' and mentions the requirement of exact text match.

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 provides basic guidelines: requires exact message text and confirmation via confirm=true. However, it does not explicitly state when to use this tool versus alternatives like delete_conversation_file, nor does it mention prerequisites or when not to use.

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