Start polling for updated host

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

Annotations already convey that the call is not read-only, not idempotent, and not destructive. The description adds that this starts polling for a specific host, but it does not disclose what happens if polling is already active, whether repeated calls are safe, or what the response indicates. This is minimal but consistent with the annotations.

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 short, but the first sentence merely repeats the title and the second adds only a small increment: 'specific' and 'after it has been updated.' The redundancy means it could be collapsed to a single sentence without losing 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 simple one-parameter state-change operation, the description covers the basic action and target, but it omits preconditions, effects of repeated calls, and the relationship to polling-lifecycle siblings. With no output schema to fill those gaps, it sits at the minimum viable level.

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 only parameter, hostId, has 0% schema description coverage, but the description's 'specific host' directly ties it to the target host. It does not clarify whether hostId is required, how to obtain it, or any expectations about the host's state, so most meaning still relies on the parameter's self-evident name.

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 uses a specific verb ('Starts polling') and resource ('a specific host'), and adds the trigger condition 'after it has been updated.' It is not a bare tautology, but it does not explicitly differentiate itself from related siblings like termix_metrics_refresh_polling or termix_metrics_start_metrics_collection, so it misses the top score.

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 phrase 'after it has been updated' implies the tool should be used when a host has been updated and polling should begin or resume. However, it provides no explicit comparison to alternatives, no exclusions, and no prerequisites, leaving the usage guidance largely implied.

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