list_eventsource_notifications

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

Annotations already cover the read-only, idempotent, non-destructive safety profile. The description adds useful context about default filtering behavior and syntax, but it does not disclose that an Eventsource connection is typically long-lived or describe what happens as events stream in. No contradiction with 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 front-loaded with the core action and endpoint, and the filter examples are well-structured and directly useful. It is slightly verbose with repeated filter examples, but each conveys a distinct case, so the length is justified.

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 single-parameter, read-only tool with output schema and strong annotations, the filtering semantics are well covered. What is missing is broader context around the streaming nature of Eventsource, authentication expectations, and how this tool relates to the websocket notification alternatives. An agent could call it correctly but may not fully understand its runtime behavior.

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 0%, so the description must carry the parameter semantics. It does so effectively by explaining the default, negation syntax, whitelist behavior, and empty-filter behavior. The only flaw is a minor inconsistency: the schema names the parameter 'filter' while the description repeatedly refers to 'filters'.

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 the operation as 'Connect to Eventsource' and gives the explicit endpoint GET /:/eventsource/notifications, which identifies the resource and action. However, it does not clarify that this is a streaming/list-style operation or contrast it with the similar websocket notification siblings.

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 detailed filtering syntax but gives no guidance on when to use this tool versus alternatives like list_websocket_notifications or list_websockets_notifications. Usage context is only implied by the endpoint name, not explicitly stated.

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