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

The annotations already flag destructive=true, but the description adds meaningful behavioral context: the deletion is a 'soft-delete' rather than a hard purge, and it is scoped to the current user. It also conditions validity on the conversation being 'open or running.' Nothing contradicts the 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?

One sentence, front-loaded with the operative verb, and no filler or repetition of the title. Every phrase ('soft-delete', 'open or running', 'current user') adds useful 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?

For a simple two-parameter destructive action, the description provides the target, operation type, state precondition, and user scope; the schema covers parameter specifics. It does not describe return values or observable effects of a soft-delete, but with destructive and idempotent annotations this is a minor gap.

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 documents both parameters fully with format, pattern, and descriptions, so the 100% coverage baseline applies. The tool description adds no additional meaning about process_id or conversation_id 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 names the exact verb ('soft-delete'), the resource ('artifact-chat conversation'), and the relevant qualifiers ('open or running', 'for the current user'). This clearly distinguishes it from other delete and artifact-chat tools without requiring inspection of the schema.

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 makes the valid state ('open or running') and user scope explicit, so an agent can infer when it applies. However, it does not name the closely related alternative stopClarityArtifactChatConversation or explain when to choose this delete operation over stopping a conversation.

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