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

Annotations already mark this as read-only, idempotent, and non-destructive, so the bar is lower. The description adds valuable behavior: newest-first ordering, one row per Cycle, included fields, and the meaning of a Cycle with no status yet. No contradiction with annotations.

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 three sentences with no wasted words. It front-loads the core behavior and output, then adds usage context and a pointer to related documentation, all in an efficient structure.

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?

There is no output schema, so the description carries the burden of explaining the return shape; it does so clearly with fields, ordering, and status semantics. It also gives filtering guidance, an alternative tool, and a doc pointer, making it complete for the tool's complexity.

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 schema already documents limit, since, and until with formats and constraints. The description adds contextual value by suggesting since/until/limit for pattern spotting, but it does not add meaning for monitorId or projectId beyond what their names imply.

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 and resource ('List a Monitor's Cycles'), specifies ordering ('newest first'), and describes the row-level fields returned. It clearly distinguishes this from the sibling get_monitor_cycle_detail by framing this as the overview listing tool.

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 names the exact use case: spotting patterns like flapping, slow drift, or regional failures. It also names the alternative tool for deeper investigation ('drill into one Cycle's full metrics and failure message with get_monitor_cycle_detail'), giving clear routing guidance.

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