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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it explains the ordering (flips conversation to `open` first), the consequence (late webhooks from the interrupted run are dropped as stale), and the soft guarantee ('best-effort' cc-server interrupt). It omits auth/permission requirements and what state the conversation is left in afterward.

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?

Two compact sentences with the state flip front-loaded ahead of the interrupt; every clause carries information (ordering, staleness handling, best-effort caveat). No filler or redundancy.

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 destructive mutation with no output schema, the description covers the mechanism and failure semantics well enough to call it correctly. The remaining gap is parameter explanation (0% schema coverage), which an agent must infer purely from the UUID property names.

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% for both required parameters, so the description carries the full burden and provides nothing: it never mentions process_id, conversation_id, their UUID format, or whether either may reference a finished turn. The word 'conversation' appears only in prose, not as parameter documentation.

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?

States a precise verb+resource ('Stop an in-flight artifact-chat turn'), which cleanly separates it from deleteClarityArtifactChatConversation (removes the conversation) and the list/get message siblings. It does not, however, explicitly name those alternatives or contrast its scope against them, so the differentiation is inferable rather than stated.

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 phrase 'in-flight' implies the condition for use (a turn is currently running), but there is no explicit when-to-use guidance, no statement of when NOT to use it, and no pointer to delete/list alternatives. Usage is implied rather than directed.

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