mark_notifications_read

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

The description states that already-read notifications keep their original read_at, adding behavioral context. However, without annotations, it does not disclose other traits like idempotency, side effects, or required permissions.

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 extremely concise, using three sentences to convey purpose, parameter usage, and a behavioral note. No unnecessary words.

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 tool with one parameter and no output schema, the description covers the main action and parameter usage. It could mention error handling or response, but overall it is fairly 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?

The description explains that cursor comes from a list_notifications response and gives an example ('ts_...'), adding significant meaning beyond the schema which only says string type.

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 'Mark all notifications at or before the cursor timestamp as read.' It uses a specific verb and resource, and distinguishes from list_notifications which retrieves notifications.

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 advises to use the cursor from list_notifications, giving explicit context for when to use the tool. It also notes behavior for already-read notifications, but does not mention alternatives or when not to use it.

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