notifications_read_all

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 states the operation is idempotent and resets the unread count to zero, which are useful behavioral disclosures. Mentioning idempotency adds meaningful transparency for an agent considering repeated calls. Could additionally mention whether it returns a count or ack, but what's present is solid.

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?

Three sentences, zero filler. Each sentence earns its place: action+scope, effect on unread count, idempotency guarantee. Efficient and front-loaded.

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, no-output-schema tool, the description is complete. It covers scope, side effects (unread count reset), and idempotency behavior. The absence of output schema means return values are unaddressed, but for a bulk mark-read operation this is a minor gap. With no annotations, the description does sufficient work.

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, and schema coverage is 100% (trivially complete). The description correctly notes there are no parameter requirements. With no parameters, there is nothing for the description to add beyond confirming the no-argument nature, which it effectively does.

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 verb ('Mark all notifications as read'), the resource (notifications), and the scope (all for authenticated user). It distinguishes from siblings like notifications_mark_read (singular) and notifications_unread_count (read-only count).

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 notes 'in a single operation' and 'for the authenticated user,' giving context on scope and batching. It implicitly distinguishes from notifications_mark_read (single) but does not explicitly name alternatives or state when not to use it. Adequate but not explicit.

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