mark_all_notifications_read

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

Annotations already provide idempotent=true, readOnlyHint=false, destructiveHint=false. The description adds that it marks all unread as read and returns a count, giving context beyond annotations without contradiction.

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 with clear verb and object, zero waste. Front-loaded with action.

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 no-parameter tool with annotations and output schema, the description fully covers purpose, behavior, and return value. No gaps.

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?

No parameters exist (baseline 4). The description does not need to add parameter info, and schema coverage is 100%.

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 unread notifications as read') and the resource ('notifications'), and also specifies the return value ('Returns the count'). This distinguishes it from siblings like mark_notification_read (single notification) and archive_all_notifications (archive vs read).

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 bulk usage but lacks explicit guidance on when to use this tool versus alternatives like mark_notification_read or archive_all_notifications. No exclusions or context provided.

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