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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful "recent" scoping qualifier (a bounded, not full, history window), but says nothing about pagination, result ordering, or what a check record contains beyond what the output schema would show.

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?

Two tight sentences with the core action front-loaded and the routing hint second. No filler, no repetition of the title or schema.

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 single-parameter read tool with an output schema and read-only/open-world annotations, the description covers what the tool returns and where to get the ID. The only gap is the imprecise definition of "recent," which slightly limits expectations about result scope.

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 single required string parameter is already documented, so the schema carries the load. The description adds no format or sourcing detail for the ID beyond pointing at monitors_list, which is baseline-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 pairs a specific verb ("List") with a precise resource ("recent check history for a website-change monitor ID"), so an agent immediately knows this returns historical check results, not monitor configuration. It is distinguishable from monitors_list and monitors_get by contrast.

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 provides explicit routing, naming monitors_list for discovery and monitors_get for configuration, which frames this tool as the one to use once an ID is known. It stops short of a full when/when-not statement (e.g., nothing about how much history is returned or when history is unavailable).

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