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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: unread_count is the full unread total regardless of the filter applied, and pagination metadata is returned for the current filter. That subtlety would be easy to get wrong otherwise.

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?

Docstring layout with Args and Returns is well organized and front-loaded with the one-line purpose. Every line carries information, though the Args/Returns scaffolding is slightly more verbose than a prose equivalent would need to be.

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 responsibly documents the return payload including unread_count, total_count, has_more, offset, and limit. The main remaining gap is that it does not describe what fields an individual notification object contains.

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 0%, so the description must carry the burden and largely does: it explains unread_only's meaning and default, limit's default and max (100), and offset's pagination role. Only the absence of any note about ordering or accepted ranges below zero keeps it from a 5.

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 (notifications) scoped to the user, which is unambiguous. It does not explicitly differentiate itself from siblings like get_unread_notification_count or mark_notification_read, but the verb+resource pairing is clear enough to place it.

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 unread_only default and pagination params, and the reader can infer this is the general listing tool. However, it never says when to use this versus get_unread_notification_count or when filtering is unnecessary, and no alternatives are named.

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