Alerts

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

readOnlyHint=true already declares the safety profile, and the description adds real behavior: the tool returns a browser_url and instructs how to surface it as a clickable link. It also conveys the breadth of what the server watches in the background. It stops short of describing pagination, latency, or how the acknowledge/clear affordances are triggered.

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?

Front-loaded with the verb and resource, and the parenthetical enumeration is informative rather than padded. The trailing browser_url rendering instruction is slightly operational noise but useful enough to keep.

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 no output schema, the description compensates by naming the returned browser_url and its intended use, and by summarizing the view's contents. Nothing critical is missing for a parameterless view-open tool, though the relationship to alerts_data/alerts_badge remains unstated.

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 takes zero parameters and schema coverage is 100%, so the baseline of 4 applies. There is no parameter behavior left to explain.

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?

States a specific verb and resource ('Open the Alerts view') and enumerates the alert categories it surfaces (long queries, failed pipelines, node memory/disk thresholds, nodes offline). This clearly distinguishes it as a view-opening tool, but it does not explicitly differentiate itself from siblings like alerts_data or alerts_badge.

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?

Usage is only implied: the agent can infer this opens the Alerts UI, but there is no explicit when-to-use versus alternatives (alerts_data, alerts_check_now, alerts_badge) or any stated preconditions. An agent must guess whether it wants the view or the underlying data.

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