zabbix_detectar_lacunas_coleta

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

No annotations are provided, so the description carries the full burden and delivers almost nothing: it does not say whether this is a read-only analysis, how a 'gap' is defined, what the tolerance multiplier does, or what happens with sparse/absent history. The only behavioral signal is the verb 'identificar', which implies a non-mutating inspection.

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?

It is a single short sentence with no filler, but it is severely under-specified rather than compact, and the leading artifact '29.' is noise that carries no meaning for tool selection.

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 need not be explained, but for a 4-parameter analytical tool with no annotations and zero schema coverage the description is far too thin. It should at minimum define the time units, the gap-detection tolerance, and the read-only nature of the call.

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% across 4 parameters, and the description mentions none of them. The time window (tempo_de/tempo_ate as integers, units unspecified — epoch seconds?) and especially tolerancia_multiplicador (default 3, purpose unexplained) are left for the agent to guess.

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: 'Identificar lacunas temporais (gaps) na coleta de um item', which tells an agent exactly what analysis is produced. However, it does not differentiate itself from nearby siblings such as zabbix_verificar_coleta and zabbix_diagnosticar_coleta, which cover overlapping collection-health territory.

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 description gives no when-to-use condition, no prerequisite (e.g., item must exist and have history), and no pointer to the alternative tools for collection diagnostics. Usage is only inferable from the single noun phrase 'lacunas na coleta'.

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