mark_thread_read

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

No annotations are provided, so the description carries full burden. It states the tool performs a mutation ('Mark... as read'), implying it changes state, but doesn't disclose important behavioral traits like whether this requires specific permissions, if the change is reversible, what happens on success/failure, or any rate limits. The description is minimal and lacks operational context.

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?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool with one parameter.

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?

Given the tool has an output schema (which handles return values) and 100% schema coverage for its single parameter, the description is minimally complete. However, as a mutation tool with no annotations, it should ideally provide more behavioral context about permissions, side effects, or error conditions to be fully helpful to an agent.

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 100%, with the single parameter 'thread_id' well-documented in the schema as 'Notification thread ID'. The description doesn't add any additional meaning beyond what's in the schema, such as format examples or where to obtain thread IDs. With high schema coverage, the baseline of 3 is appropriate.

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 clearly states the action ('Mark') and target ('a specific notification thread as read'), providing a specific verb+resource combination. However, it doesn't differentiate from the sibling tool 'mark_notifications_read', which appears to serve a similar purpose but with potentially different scope.

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 provides no guidance on when to use this tool versus alternatives like 'mark_notifications_read' (which might mark multiple notifications as read). It also doesn't mention prerequisites, such as needing an authenticated user context or having appropriate permissions to modify notification status.

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