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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds scope ('THIS operator's'), filters out Terminal/ACP Groks, describes output labels, and notes the send path via create_attention_directive even for quiet seats. No contradiction with 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?

First two sentences are efficient and front-loaded with purpose and usage. The final sentence about create_attention_directive and 'the sticky waits' is jargon-heavy and tangential to the listing behavior, costing it a perfect score.

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 optional-parameter list operation with no output schema, the description communicates scope, selection mode, and return labels. It doesn't detail pagination or the exact meaning of 'last turns', but schema covers parameters and annotations cover safety, so it is reasonably complete.

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?

Input schema covers all 3 parameters with 100% description coverage, so baseline 3. Description restates the seat behavior ('Omit seat to list; pass a slug') and limit's dual role, but does not materially add 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?

Description opens with a specific verb and resource: 'List THIS operator's Grok Bot desktop chat seats' and explicitly excludes 'Terminal/ACP coding Groks'. It also names the output labels ('live/quiet/gone') and 'last turns', making it distinct from sibling list tools like list_x_chat_conversations.

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?

Explicitly says 'Use when they ask to see or talk about their Grok Bots', a clear conditional trigger. It also gives parameter guidance ('Omit seat to list; pass a slug for one seat') and routes send requests to create_attention_directive, naming an alternative tool.

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