Mark notifications read or unread

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

Goes beyond annotations by describing the return structure (marked, read, ids, message), the 204 No Content behavior, the meaning of 'marked', the idempotent retry safety, the notification id vs resource.id pitfall, and that unknown ids do not fail the call. No contradiction with annotations.

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?

Well-structured with purpose, usage, returns, pitfalls, and cross-references. Every sentence adds value; while longer than a minimal description, the complexity of the API (204, idempotency, id pitfalls) justifies the length. Slightly dense but not wasteful.

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?

With 2 well-documented params, annotations, an output schema, and rich behavioral guidance, the description fully equips the agent to select and invoke the tool correctly. Includes all necessary caveats and alternatives.

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?

Schema already covers both parameters with descriptions (100% coverage), so baseline 3. The description adds critical semantics: ids come from the 'row id' of list_notifications, not resource.id, and clarifies the 'read' direction is safe with explicit ids.

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?

States 'Mark specific notifications read (or unread) in one bulk request' – a specific verb+resource. Distinguishes from siblings by calling itself the 'id-consuming counterpart of list_notifications' and differentiating from mark_all_notifications_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?

Explicitly says 'Use it after you have actually handled what a notification was about' and provides cross-references: 'get the ids from list_notifications' and 'to clear an entire inbox use mark_all_notifications_read'. This is clear when-to-use and alternatives.

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