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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context beyond the annotations: what kinds of alerts appear, that there is no delete tool, and that notification_mark_read clears the badge. It does not describe return fields or pagination, but those are secondary for a zero-parameter notification list.

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 tightly written sentences, front-loaded with the resource and examples. Each sentence adds distinct value: examples, diagnostic use case, sibling exclusions, and the related mark-read action.

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 zero-parameter, non-destructive list tool with rich annotations and no output schema, the description supplies everything an agent needs to decide whether to call it. It covers content, exclusions, diagnostic relevance, and the badge-clearing alternative without unnecessary return-value detail.

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 tool takes zero parameters, and the schema is fully specified with additionalProperties false. There is no parameter semantics for the description to explain, so the baseline of 4 for a zero-parameter tool is appropriate.

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 the specific resource (in-app notifications) and gives concrete examples of what appears there, such as disconnected accounts and limits hit. It explicitly distinguishes notifications from prospect replies in conversation_list and to-dos in task_list, so an agent can identify the right tool without opening the schema.

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?

It states when the tool is useful: reading notifications is worth doing when diagnosing why a campaign stopped. It also names the alternatives for adjacent concepts (conversation_list for prospect replies, task_list for to-dos) and points to notification_mark_read for clearing the badge.

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