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

Annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) already declare this can mutate external state without being safe to retry. The description surfaces the two execution modes, which is genuinely beyond the annotations, but says nothing about what a trigger actually does (open PRs? post comments? notify agents?) or that it is non-idempotent, which matters here.

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 front-loaded sentences: capability first, then the monitor inventory. The eight-item list is long but earns its place by telling the agent what the tool covers; there is no filler.

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?

An output schema exists, so return values needn't be explained. However, with a mutating trigger path and an undocumented entity_id, the definition leaves out information the agent needs before invoking it on a live system.

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 both parameters depend on the description. 'trigger_check' is only obliquely implied by 'trigger a manual heartbeat check cycle', and 'entity_id' is never mentioned at all — the agent cannot tell whether it takes a repo, org, agent, or monitor ID.

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 monitor status') plus a second mode ('trigger a manual heartbeat check cycle'), and enumerates the eight monitors so the agent knows the domain covered. No sibling overlap exists among the listed tools, so differentiation is a non-issue rather than a gap.

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 two modes are named but not disambiguated: nothing says when an agent should just read status versus when it should trigger a check cycle, nor what entity_id scopes. Usage is implied by the mode names only, with no exclusions or preconditions.

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