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

readOnlyHint=true already establishes the safe read profile, so the bar is lower. The description adds value by disclosing what each record carries (status, period, ping URL) — useful given there is no output schema — but says nothing about pagination behavior or uptime-skip side effects.

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 well-formed sentence with the resource and concept front-loaded, plus a compact API hint ('StatusCake: GET /heartbeat'). No filler; the parenthetical definition earns its place, though the trailing endpoint reference is marginally 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 read-only, zero-required-parameter list tool with 100% schema coverage and no output schema, the description is nearly sufficient: it names the resource, the concept, and the fields returned. It could add a note on pagination/result size to be fully complete.

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%, so the schema fully documents all 6 parameters (page, tags, limit, status, matchany, nouptime). The description mentions none of them, so per the rubric the baseline 3 applies — the schema carries the full parameter burden.

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?

States a specific verb+resource ('List heartbeat (push) checks'), defines the concept ('jobs that must ping a StatusCake URL within a period'), and enumerates returned fields (status, period, ping URL). It is trivially distinguishable from the single-check sibling statuscake_get_heartbeat_check and from statuscake_list_uptime_checks by resource.

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 by the verb 'List' — an agent can infer it returns all heartbeat checks. However, no when-to-use/when-not guidance or alternative routing (e.g. 'use get_heartbeat_check for a single check') is provided, leaving scope inference to the caller.

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