Mark All Notifications Read

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

The description implies a mutation (marking as read) but does not disclose any behavioral traits such as idempotency, scope (user-specific?), or reversibility. With no annotations, the description carries full burden but provides minimal detail.

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 sentence that is concise and to the point. Every word serves the purpose, with no redundancy.

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 side-effect tool with no parameters and no output schema, the description adequately conveys the core action. However, it omits information about return value or confirmation, but this is acceptable given the simplicity.

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?

There are 0 parameters, so the input schema already covers everything. The description adds value by confirming that the action applies to 'all notifications' without filters. Schema coverage is 100%, so a baseline of 3 is appropriate, and the description slightly enhances clarity, earning a 4.

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 all notifications as read', using a specific verb and resource. It distinguishes from sibling tools like 'list_notifications' which merely list notifications without modifying them.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'list_notifications' for reading). There is no mention of prerequisites 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.