mark_notifications_seen

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

Disclosures beyond annotations: marks notifications as seen, persists cursor server-side, requires authentication, subject to rate limiting. No contradiction with annotations (destructiveHint=false, idempotentHint=false).

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?

Four sentences, no redundancy. Front-loaded with primary purpose, followed by important usage details. Every sentence provides value.

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 presence of an output schema (not shown but indicated), the description adequately covers the effect, prerequisites, and post-conditions for a simple tool with one optional parameter.

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?

Input schema has 100% coverage with description of seenAt. The description restates 'ISO 8601 timestamp; defaults to now' without adding new meaning beyond the schema, aligning with baseline 3.

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', the resource 'notifications', and the specific effect 'as seen up to a timestamp', distinguishing it from get_notifications which retrieves notifications.

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?

Explicitly mentions authentication requirement, rate limiting, and the server-side persistence of the seen cursor, guiding the agent to use get_notifications after marking. It implies when not to use this tool (e.g., when you don't want to mark notifications).

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