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

With no annotations, the description must carry the burden of behavioral disclosure. It implies a read-only snapshot but doesn't explicitly state it, nor does it mention any side effects, caching behavior, or data freshness. It does describe the content returned, which is useful, but leaves out potential characteristics like latency, pagination, or error handling.

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, tightly written sentence. It front-loads the access restriction ('Admin only') and then lists the core data points. No filler words; every clause adds value. This is exemplary conciseness.

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 zero-parameter tool with no output schema, the description provides a clear list of data categories (alerts, balance, issues). It covers the essential 'what' and 'why' (needs attention). While it could mention freshness or how to interpret severity levels, the simplicity of the tool means this is largely sufficient. The note 'Admin only' also adds necessary context for access.

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 has zero parameters, so the input schema provides no semantic burden. Per the guidelines, a baseline of 4 is appropriate since the description doesn't need to compensate for missing parameter documentation. The description focuses on outputs, which is effective.

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 that the tool reports current operational state including alerts by severity, gateway balance, and known issues. It uses specific verbs and resources, and while it doesn't explicitly distinguish from siblings like ops_pulse, the focus on 'needs attention right now' gives it a distinct purpose.

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?

It provides an access restriction ('Admin only') but no explicit guidance on when to use this tool versus alternatives such as ops_pulse or ops_route_quality. The phrase 'known issues that need attention right now' implies urgent operational monitoring, but it doesn't clearly state exclusions or alternative use cases.

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