mark-done

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

Description details actions (archive, markRead, clearUnread) but does not explicitly mention consequences like irreversibility despite destructiveHint=true. Adds context beyond annotations (e.g., clearUnread requires workspaceId). No contradiction.

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 sentences with no fluff. First sentence states main purpose, second details options. Front-loaded and efficient.

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?

Covers all capabilities (individual vs bulk, thread vs conversation, actions). Output schema likely handles return values. Could mention prerequisites for clearUnread, but schema covers it.

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%, so baseline is 3. Description adds meaningful grouping of parameters by type (thread vs conversation) and explains how they interact, e.g., clearUnread requires workspaceId.

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?

Clearly states verb 'mark' and resources 'threads or conversations'. Distinguishes between thread and conversation actions, and from sibling tools like 'reply', 'react', 'create-thread', and 'delete-object' by focusing on marking as done.

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?

Provides explicit guidance on using specific IDs vs bulk selectors (workspace or channel). Differentiates between thread and conversation options. However, does not explicitly state when not to use this tool or compare to alternatives like 'delete-object'.

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