list_notifications

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

There are no annotations, and the description does not disclose pagination behavior, return format, ordering, or whether this is a safe read operation. The only hint of behavior comes from the parameter schema (page/per_page), which is not part of the description itself.

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 extremely concise with zero wasted words, but it is a fragment rather than a complete sentence. It is front-loaded and easy to parse, though it lacks the structural completeness that would make it a 5.

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 there is no output schema and no annotations, the description must compensate by explaining what notifications are, how they are returned, or how they relate to other notification features. It fails to do so, leaving the tool's behavior underspecified for an agent.

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 input schema already provides descriptions for both parameters (page and per_page) with 100% coverage. The description adds no additional semantic value beyond what the schema states, so the baseline of 3 applies.

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 "List notifications" uses a specific verb and resource, clearly indicating a read-only listing operation. It is distinguishable from the sibling tool get_notification_count, which counts rather than lists, though it does not explicitly differentiate itself from other list_* tools beyond the resource name.

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?

No guidance is provided about when to use this tool versus alternatives, nor are any prerequisites or context given. The description simply states the action without explaining scenarios where listing notifications would be appropriate or how it relates to notification count.

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