list_monitor_notification_rules

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

With no annotations, the description carries the full burden. It correctly identifies a read operation ('List') but does not disclose any behavioral traits such as pagination behavior (despite page_size/page_offset parameters), authentication needs, rate limits, or whether the list is exhaustive.

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 very short (one sentence, 9 words), which is concise but may be too terse given the lack of parameter information and behavioral context. It lacks structured elements like 'When to use' or parameter notes.

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 incomplete for a list-oriented tool. It omits pagination details, output format, required permissions, and any constraints. With no output schema and no annotations, the description fails to provide sufficient context for correct invocation.

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% and the description does not mention either parameter (page_size, page_offset) nor explain their meaning or usage. The agent has no context to correctly set parameters.

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 the tool lists monitor notification routing rules and specifies that it shows who gets alerted. It distinguishes from sibling tools like list_downtime_schedules or list_security_monitoring_rules by focusing on notification routing rules. However, it does not specify scope (e.g., all monitors or filterable).

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 no guidance on when to use this tool versus alternatives. It lacks any context about prerequisites, input requirements, or situations where other tools might be more appropriate.

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