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

The annotation readOnlyHint: true already establishes the tool is safe. The description adds behavioral nuance—grouped mode disables paging and includeStats adds 24h uptime, p95 latency, and sparkline data—which goes beyond the annotation without contradicting it. No side effects are mentioned, but none are expected for a read-only list operation.

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 fluff. It front-loads the core action (list monitors with status), then concisely covers the two optional flags and the project context requirement. Every sentence serves a purpose.

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?

Given there is no output schema and the operation is straightforward, the description is complete. It states the core function, the key options, and the prerequisite of project context. No additional information is needed for an agent to correctly invoke the tool.

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 coverage is 100% with all parameters described, meeting the baseline of 3. The description enriches parameter semantics by explaining the grouped tree view references the sidebar and notes the paging exception, and elaborates on includeStats output. This adds meaningful context beyond the parameter 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 clearly states the tool's purpose: 'List the monitors of a project with their current status.' It uses a specific verb and resource, and the name distinguishes it from siblings like get_monitor (singular) and list_monitor_checks (checks for monitors). No ambiguity exists about what the tool does.

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 implied usage (e.g., grouping, stats options) but does not explicitly mention when to use this tool versus alternatives such as get_monitor for a single monitor or list_monitor_checks for monitor checks. It does note 'Requires project context,' which is useful, but lacks explicit when-not guidance.

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