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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: it is silent on pagination behavior, ordering, whether results are unread-only, or how the categories map to the tab parameter.

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 short sentence with no filler, and the content categories are front-loaded. It is terse to the point of under-specification, but nothing in the text is wasted.

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?

For a list tool with three undocumented parameters, no output schema, and no required fields, the description should at minimum explain the tab values and confirm pagination via cursor. Without that, an agent cannot reliably page through results or choose a tab, making the definition inadequate for the tool's actual complexity.

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% across three parameters, so the description carries the burden and largely fails. The three named categories ('mentions, finished work and blocked monitors') may hint at the legal values of 'tab', but the mapping is never stated, and 'limit' and 'cursor' (pagination) are not mentioned at all.

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 states a concrete reading action and enumerates the content categories surfaced (mentions, finished work, blocked monitors), which goes beyond restating the name. It does not, however, distinguish this from look-alike siblings such as list_activity or list_notes, so an agent still has to guess which list tool is right.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many list_* siblings. The only signal is the implicit 'these are notifications' framing, leaving the agent to infer that this is the inbox-style read versus an activity log.

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