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

No annotations are provided, so the description must carry the behavioral burden. It does say the call returns one page of check summaries plus pagination metadata, which is useful return-shape context, but it does not state read-only/safe semantics, auth or permission needs, rate limits, or default page size.

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 no filler. The core purpose comes first, then the return shape, which is exactly the order an agent needs.

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 and no annotations, and all four parameters are undocumented in the schema. The description covers the return shape and paging concept, which helps, but it leaves the required id parameter and the offset/limit contract unexplained.

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 0%, so the description has to explain the four parameters. It only hints at limit ("bounded by a result limit") and status ("filtered by status"), and says nothing about what id identifies (the monitor) or how offset interacts with limit for paging.

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 gives a specific verb and resource: "List historical checks for a monitor." That is clearly distinct from the singular sibling firecrawl_monitor_check and from firecrawl_monitor_get (config), though neither sibling is named explicitly.

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 mentions optional status filtering and a result limit, so usage is implied. But it never says when to use this instead of firecrawl_monitor_check for a single check, nor does it give any exclusions or prerequisites (for example, whether the monitor must exist).

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