Update Notification

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

No annotations are provided, so the description carries the full burden. It only discloses the basic update action and an ID lookup hint, but does not mention potential side effects such as applyExisting pushing changes to all existing monitors, permissions required, or whether the update is reversible.

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 two sentences with no filler. The core action is front-loaded, and the second sentence provides a useful cross-reference to a sibling tool for obtaining the required ID.

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?

The description is minimal, but the schema and output schema cover the parameter and return details. It lacks explicit mention of the potentially wide-reaching applyExisting behavior and does not fully explain when to use this tool over addNotification, but it provides enough orientation for a basic update operation.

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 100%, so the baseline is 3. The description adds value by telling the agent how to source the required notificationID via listNotifications, and it frames the resource as a notification channel, complementing the schema's field descriptions.

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 ('Updates') and a specific resource ('existing notification channel'), clearly indicating an update operation. The word 'existing' distinguishes it from creation tools like addNotification, and the sibling context confirms the resource type.

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 an explicit prerequisite: use listNotifications to find the notification ID. It implies the tool is for modifying an existing channel rather than creating or deleting one, though it does not explicitly name addNotification or deleteNotification as alternatives.

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