list_notifications

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

Annotations already declare readOnlyHint=true, and the description confirms no side effects ('leaves read state unchanged'). It also mentions pagination and optional filtering, adding behavioral context beyond what annotations provide.

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 three sentences: purpose, usage note, sibling differentiation. No redundant words, front-loaded with core function, and structured for quick parsing.

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?

Without an output schema, the description covers pagination, filtering, and non-mutating behavior. It provides enough context for inbox triage and distinguishes from related tools, though it could mention result ordering or total count.

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 input schema covers 67% of parameters with descriptions (offset and pageSize have descriptions; unreadOnly lacks one in schema). The description adds meaning for unreadOnly ('optionally unread only') but does not elaborate on offset or pageSize beyond schema defaults.

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 tool's function: 'List paginated in-app notifications for the authenticated user, optionally unread only.' It uses a specific verb ('list') and resource ('notifications'), and distinguishes from siblings like get_notification and mark tools.

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 explicitly says when to use this tool ('Use for inbox triage') and when not ('this leaves read state unchanged. Use get_notification for one item's details and mark tools only after review'), providing clear context and alternatives.

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