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

readOnlyHint=true already covers the safety profile, and the description adds the underlying endpoint (GET /api/v2/heartbeats) plus the attributes returned (period, grace, status values up/down/paused/pending), which is genuinely useful context. It does not mention pagination behavior, result ordering, rate limits, or the global-token requirement implied by team_name.

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 sentences, zero filler. The resource and its domain meaning come first, followed by the response attributes and endpoint — everything is front-loaded and each clause carries information.

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 paginated list with a fully described schema and no output schema, the description covers what the tool returns and where it maps in the API. The only real gap is a note on pagination/result limits and the token scoping around team_name, which the agent must infer.

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 page, per_page, and team_name are fully documented in the schema; baseline 3 applies. The description mentions period, grace, and status, but those are response fields rather than parameters, so it adds no parameter meaning beyond the schema.

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 and resource ('List heartbeats') and goes further by defining what a heartbeat is ('cron/background-job monitors that expect a periodic ping'), which disambiguates it from the monitor/incident siblings. It never names a sibling tool or contrasts scope with them, so it stops short of a 5.

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 rather than stated: the parenthetical definition tells the agent this is the tool for cron/background-job monitors, which subtly separates it from betterstack_list_monitors, but there is no explicit 'use this when…' or 'do not use for…' guidance and no mention of pagination strategy or token prerequisites.

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