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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description usefully names the data returned (status, response time, error), which substitutes for the missing output schema, but says nothing about ordering, retention window, or what happens when a monitor has no checks.

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?

A single efficient sentence with no filler, front-loading the action and resource. The parenthetical of returned fields is compact and informative rather than redundant.

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 simple two-parameter read-only tool with full schema coverage, the description covers the action, the target resource, and the returned fields, which compensates for the absent output schema. Minor gaps like ordering and empty-result behavior are not fatal.

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 100%: both monitor_id and limit are documented in the schema, including the 1-100 range and default of 20. The description adds no parameter semantics beyond that, so the baseline 3 applies.

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 clear verb-and-resource pair ('List the most recent checks') and scopes it with 'for a monitor', plus it lists the returned fields (status, response time, error). It does not explicitly distinguish itself from siblings like get-monitor, but the sibling set has no true overlap, so the purpose is unambiguous.

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?

Usage is implied: an agent can infer this is the tool for inspecting a monitor's recent check history after identifying a monitor_id. There is no explicit when-to-use statement, no exclusions, and no mention of get-monitor or list-incidents as alternatives for broader health context.

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