mark_notifications_read

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly indicates a state-changing action ('mark as read'), but it does not describe side effects, reversibility, or what happens to already-read threads. The absence of annotations makes this a moderate rather than strong disclosure.

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 front-loaded sentence with no filler. 'Mark all notification threads as read' conveys the action, object, and outcome efficiently without under-specification.

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 zero-parameter tool with an output schema, the description covers the essential behavior succinctly. It could add an explicit link to get_notifications or clarify the 'all' scope, but these are minor gaps for such a simple imperative tool.

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 tool has zero parameters, so the input schema fully describes the argument surface. The description adds no parameter detail because none is needed; this is the appropriate baseline for a no-parameter tool.

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 uses a specific verb ('mark') and a clear resource ('all notification threads') with an explicit outcome ('as read'). This clearly distinguishes it from sibling tools like get_notifications, which only retrieve notifications rather than changing their state.

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 used when the agent needs to clear the unread state of all notification threads. However, it does not explicitly state when to choose this over alternatives, nor does it mention any limitations such as inability to mark a single thread as read.

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