Mark notifications as read

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It states the action but does not disclose side effects or scope implications (e.g., that it affects all notifications for the authenticated user, is irreversible, or requires specific permissions). The word 'mark' implicitly suggests a mutation, but no safety or consequence details are provided.

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 redundant content. It immediately states the action and target, achieving maximum conciseness.

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?

Given the tool's simplicity (no parameters, no output schema), the description is close to sufficient. However, the lack of usage context and behavioral transparency leaves gaps that could affect an agent's decision to invoke it safely and correctly among siblings. The description is adequate but not comprehensive.

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 the schema is empty with 100% coverage. Per rubric, the baseline for 0 parameters is 4. The description adds no parameter information, but none is needed.

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 a specific action ('mark') on a specific resource ('all current notifications') with a defined outcome ('seen'). It is distinguishable from sibling tools like bluesky_get_notifications, which retrieves notifications, and other mutation tools with different targets.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of typical workflows (e.g., after reading notifications) or exclusions. Sibling tools are not referenced, and no context signals indicate preferred usage.

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