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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is not needed for safety disclosure. It nonetheless adds real context beyond them: deletion filtering, ordering by name, inclusion of unselected/disabled rows, the meaning of IsChecked and IsDisabled, and an explicit statement of what is NOT returned.

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?

The description is four short sentences, front-loaded with the core operation and then the field semantics, with no filler or repetition. The only minor inefficiency is that the field semantics (IsChecked/IsDisabled) could have been grouped more tightly with the scope sentence.

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?

With no output schema, the description carries the burden of explaining return values, and it does explain the two flag fields that matter plus the absence of user preference data. It stops short of enumerating the other fields on an integration record, but the critical decision-making fields are covered for a simple one-parameter read tool.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that heartbeatExternalId is the GUID returned as Id by HeartbeatList. The description adds no further syntax, format, or sourcing guidance, so the baseline of 3 applies.

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 all non-deleted organization integrations for a non-deleted heartbeat') plus scope details (includes unselected and disabled, ordered by name) that make it distinct from a plain integration list. It falls short of a 5 only because it never names the sibling it should be chosen over, such as integration_list or monitor_notifications_get.

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 agent can infer this is the tool for seeing which integrations are assigned to a heartbeat, but there is no explicit 'use this when...' or 'use X instead' routing. The closing exclusion about user-specific notification preferences is the only boundary signal provided.

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