monitor

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

With no annotations, the description carries the full behavioral burden, yet it never says whether this is read-only, whether it mutates or acknowledges approval gates, whether output is a snapshot or stream, or whether it is safe to poll. Only the term 'Heartbeat' gestures at snapshot semantics.

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 six words and front-loads the only concept it has, so it is not padded. However, it is under-specified rather than concise: the colon-fragment structure omits the verb that would make the purpose actionable.

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, no annotations, and no parameters, so the description is the sole source of information and it is too thin to tell an agent what a call returns or how to use the result. Missing are the return shape, the meaning of 'open approval gates', and whether action is expected on them.

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?

The tool takes zero parameters and the input schema has an empty properties object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description neither adds nor omits parameter information.

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 phrase 'Heartbeat: statuses and open approval gates' hints at what the tool returns (status snapshot plus pending approvals) but never states an action or verb, and gives no hint of how it differs from siblings like list_cases or focus_directives. Purpose is inferable but vague.

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?

There is no statement of when to call this tool versus run_all, focus_directives, or list_cases, and no mention of polling cadence or prerequisites. Only the word 'Heartbeat' loosely implies a periodic status check; the agent must guess.

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