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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds two behavioral facts beyond that — results are returned newest-first and an unread count is included — which is genuine extra context, but nothing about pagination limits or how the unread count relates to the listed items.

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?

A single sentence that front-loads the resource and packs the ordering and unread-count detail without filler. Every clause earns its place.

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 no output schema, the description carries the burden of describing the return, and it does name the result set, ordering, and the unread count field. Pagination behavior is covered by the schema, so the only remaining gap is that the description doesn't indicate whether additional totals or a total-count are returned.

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 description coverage is 100%: page (1-indexed, default 1) and page_size (default 20, max 50) are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 a specific verb (List) and resource (the user's MisarPost notifications), and adds scope detail: what kinds of notifications (publish results, account problems), the ordering (newest first), and an included field (unread count). This clearly separates it from the sibling mutation tools mark_notification_read and 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?

Usage is implied by the verb and resource — an agent can infer this is the read path for notifications, and the presence of mark_notification_read/mark_all_notifications_read siblings makes the read-vs-mutate split natural. However, the description never explicitly says when to use this versus those siblings, nor does it state any prerequisites such as authentication or workspace scoping.

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