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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description adds meaningful behavioral context beyond annotations by specifying 'current user's', 'recent', and 'non-deleted', which tell the agent this is a filtered read operation rather than a full dump of all conversations.

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, no filler, and the core action and resource are front-loaded. The scoping qualifiers ('current user's recent non-deleted', 'Clarity v2 process and snapshot kind') earn their place because they materially narrow what the tool returns.

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 read-only list operation with two well-documented parameters and safety annotations, the description is largely sufficient. It does not describe the response shape or pagination, but output schema is absent and list-tool return values are generally predictable from the resource name.

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 coverage is 100%, and both process_id and snapshot_kind already have clear descriptions plus an enum for snapshot_kind. The description reinforces that these parameters identify the process and snapshot kind but adds no new semantic detail beyond the schema.

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 specific verb ('List'), a precise resource ('artifact-chat conversations'), and clear scoping ('current user's recent non-deleted', 'for a Clarity v2 process and snapshot kind'). This clearly distinguishes it from siblings like getClarityArtifactChatMessages (messages, not conversations) and deleteClarityArtifactChatConversation (deletion, not listing).

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 implies the tool is for retrieving conversation summaries for a given process and snapshot kind, but it does not explicitly say when to prefer this over alternatives like getClarityArtifactChatMessages or listClarityProcessSnapshots. It provides clear context about scope (current user, non-deleted, recent) but no exclusions or routing guidance.

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