list_notification

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and 'Read' plus 'GET' is consistent with those. The description adds little behavioral context beyond the endpoint, such as whether the response is a list or whether pagination applies, but the annotations and output schema reduce the severity of that gap.

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 short, front-loaded, and contains no filler: 'Read Notification' followed by the HTTP endpoint. For a zero-parameter read tool, this is appropriately sized and easy to scan.

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 the empty parameter schema, the safety annotations, and the presence of an output schema, the description is mostly sufficient for invoking the tool correctly. The main remaining gap is that it does not explicitly state the list semantics or route users away from sibling notification tools, but no required inputs are missing.

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 has zero properties and the description adds no parameter detail, so there are no undocumented inputs. With zero parameters, the baseline of 4 applies even though the description does not expand on parameter semantics.

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 uses a specific verb ('Read') and resource ('Notification') and includes the exact GET endpoint, so an agent can recognize a read operation on the notification resource. However, it does not explicitly say 'list all notifications' or differentiate itself from get_notification_by_id and list_notification_schema, so sibling differentiation is left to the tool name and path.

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 gives no guidance on when to use this tool versus alternatives. There is no mention of get_notification_by_id for reading a single notification or list_notification_schema for discovering schema details; the only implied signal is the collection-level GET path.

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