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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail that the listing is 'paginated', which is useful context. However, it does not mention default ordering, whether both read and unread notifications are returned by default, or any other operational behavior beyond pagination. With annotations covering the read-only nature, a 3 is appropriate.

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 a single, concise sentence that front-loads the primary purpose ('List in-app notifications') followed by the scope and pagination detail. There is zero fluff or redundant wording, and every word 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?

Given that an output schema exists, the return format is covered. The description is minimal but sufficient for a simple list operation with well-documented optional parameters. It could add context about default filtering (e.g., whether unread notifications are shown by default) or mention that filtering by is_read and category is supported, but those are already in the schema. The description is adequate but not rich.

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 coverage is 100%, so all four parameters (page, limit, is_read, category) are already documented with descriptions in the schema. The description only adds the word 'paginated', which hints at page and limit but does not add any new information beyond what the schema provides. Baseline 3 is correct for full schema coverage with minimal description contribution.

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 clearly states the verb 'List' and the resource 'in-app notifications' with the scope 'for the account' and the qualifier 'paginated'. This distinguishes it from count_unread_notifications and clear_read_notifications, though it does not explicitly name alternatives like list_activity or list_notification_channels. The resource is specific enough for an agent to understand the tool's function.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to use count_unread_notifications for a count, mark_notifications_read for marking, or list_activity for activity logs. The usage context is only implied by the verb 'list', but no explicit when-to-use or when-not-to-use instructions are given.

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