clear_notifications

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

No annotations provided, so description carries burden. It discloses scope ('all', 'current user') which implies a bulk mutation, but does not state whether this is reversible, requires auth, or has side effects. Adequate but thin for a write operation.

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?

Single sentence, front-loaded, zero waste. Perfectly sized for a no-arg tool.

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?

Simple zero-param tool with no output schema, so minimal burden. But absence of any behavioral detail (reversibility, effect on unread counts) leaves an agent guessing about side effects.

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?

Zero parameters, so schema is empty and nothing to document. The description correctly signals no inputs are needed ('all', 'current user'). Baseline 4 per rules for 0-param tools.

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?

Specific verb+resource: 'mark all notifications as read'. Clearly distinguishes from sibling check_notifications (which presumably reads notifications rather than clearing them). No explicit sibling naming, but scope is unambiguous.

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?

Implied usage from the imperative 'mark as read for current user' but no explicit when-to-use guidance or alternative routing (e.g., vs check_notifications). Minimum viable.

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