list_notification

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

The description adds no behavioral context beyond what the annotations already state: readOnlyHint=true, idempotentHint=true, and destructiveHint=false. It does not mention pagination, filtering, authentication requirements, or what subset of notifications is returned, so it contributes nothing beyond the structured annotations.

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 very short and front-loads the core action ('Read Notification') followed by the exact endpoint. It is appropriately sized for a zero-parameter read tool, though 'Read Notification' is slightly less explicit than 'List notifications'.

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 read endpoint with an output schema and strong annotations, the description is minimally adequate. However, it does not clarify whether this returns all notifications or a single notification, and it gives no hint about when to choose this over get_notification_by_id or list_notification_schema.

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 has zero parameters, so the schema already fully covers the input space. The description does not need to explain parameter meaning, and the baseline of 4 for zero-parameter tools 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 states a specific verb ('Read') and resource ('Notification') and includes the exact HTTP endpoint, which makes clear this is a read operation on the notification collection. It does not explicitly contrast itself with siblings like get_notification_by_id or list_notification_schema, but the endpoint semantics are enough to distinguish it.

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 guidance on when to use this tool versus alternatives such as get_notification_by_id or list_notification_schema. The description only provides the endpoint, leaving the agent to infer selection criteria from sibling names.

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