gateway_notification_get

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

The description adds the auth scope 'notifications:read', which is not in annotations. Annotations already declare readOnlyHint=true, so the 'read' action is consistent. However, the description does not disclose the possible side effect of the mark_seen parameter (default true), which could imply mutation. That gap is significant but not a contradiction.

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 core action and includes the essential auth requirement. There is zero redundancy; every part adds information.

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?

With two parameters and no schema descriptions, an agent lacks crucial input guidance. The output schema exists, covering return value, but the description fails to explain how to populate the inputs. The auth requirement is useful but insufficient for a complete call.

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 description coverage is 0%, so the description must compensate. It provides no explanation of notification_id or mark_seen. The description does not help an agent understand parameter purpose or formats, making it very difficult to call the tool correctly.

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 'Read one visible notification', which is a specific verb and resource, and the singular 'one' distinguishes it from the list sibling (gateway_notifications_list). It does not explicitly name alternatives, but the purpose is unambiguous.

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 only a permission requirement and no guidance on when to use this tool versus siblings like gateway_notifications_list or gateway_notification_ack. It does not mention when to prefer this over alternatives, nor any scenarios where it should not be used.

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