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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds context about scope (up to 100 monitors) and that it returns the most recent incidents per monitor in a single call. However, it does not explain what happens beyond 100 monitors or the exact time window for 'recent', which would be useful behavioral detail.

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 efficient sentence that front-loads the action and scope. It is concise without fluff, though it could be slightly clearer about the return structure. Still, it earns its place.

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 read-only list tool with one optional parameter and no output schema, the description is adequate but leaves gaps: it does not specify time range for 'recent', behavior when the user has more than 100 monitors, or pagination. These are relevant for an agent planning to use the results.

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% and the only parameter 'limit' is fully described in the schema. The description references 'most recent incidents per monitor', which loosely aligns with the limit parameter but adds no extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'Get all recent incidents across the authenticated user's monitors.' It clearly indicates a bulk operation covering multiple monitors. However, it does not explicitly name or contrast with sibling tools like get-monitor-incidents, so an agent might not immediately know when to pick this over that one.

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 such as get-monitor-incidents or diagnose-incident. It only states what it does, leaving the agent to infer context. There are no exclusions, prerequisites, or hints about when a bulk call is preferable.

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