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

Annotations carry readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is already covered. The description adds genuinely valuable context beyond those: the default 'count every live member' behavior, how filters narrow counts, the exact 404 conditions (feature disabled, missing batch, wrong recipient/team, no matching live member), and the team_id auth nuances (API-key pinning vs OAuth multi-team). This is real behavioral disclosure, not a restatement of the annotations. No contradiction present.

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 front-loaded with the core purpose and return shape, and every sentence contributes new information. It is on the longer side (roughly 90 words) and the filter-narrowing point is made twice near the end, so it is dense but slightly redundant. Strong structure, marginally over-worded.

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?

There is no output schema, so the description correctly carries the burden of explaining the return shape (per-type live-member counts, unread count, worst severity). It covers prerequisites, auth contexts, 404 semantics, and the effect of every filter. All six parameters are documented in the schema at 100% coverage. Nothing an agent needs to call this correctly is missing.

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%, so the baseline is 3. The description adds meaning beyond the schema by tying the type/severity/minSeverity filters to the feed's narrowing behavior ('exactly as the feed narrows a batch row') and clarifying that filters affect only the counts, not which batch is returned. This raises it above baseline, though the bulk of parameter detail legitimately lives in the schema.

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 names a specific verb ('Get'), resource ('notification batch by id'), scope ('for the authenticated user'), and the concrete fields returned (per-type live-member counts, unread count, worst severity). It names its niche use cases (cold deep links, sidebar retention) and distinguishes itself from feed-returned batches, so an agent can tell it apart from siblings like getNotificationFeed, getNotification, and listNotifications without opening schemas.

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 gives clear context for when to use it — for batches the caller can no longer see in the feed — and states the prerequisite (Notification Center feature) plus the full set of 404 conditions. It implicitly marks the feed as the alternative path but does not name a specific sibling tool or an explicit when-not-to-use instruction, so it stops just short of a 5.

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