zabbix_consultar_tendencias

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

With no annotations, the description carries the full burden. 'Recuperar' implies a read, but nothing says whether it is read-only, what retention/rate limits apply, or what happens when the requested period exceeds stored trend retention — a real behavioral question for Zabbix trends.

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?

A single short sentence with the resource front-loaded; the only waste is the leading item number '26.'. Efficient, though it errs toward under-specification rather than verbosity.

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 described, but the input side is completely bare: 3 required params with no semantics, no annotations, and no guidance on period limits. For a data-retrieval tool whose correctness depends on time-unit interpretation, this is inadequate.

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 all three parameters (itemid, tempo_de, tempo_ate) are undocumented in both schema and description. The description doesn't state whether the time values are Unix timestamps, seconds, or what unit/order is expected, leaving a real ambiguity for the caller.

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 names a specific verb and resource ('Recuperar tendências (trends)'), which is enough to know it fetches trend data. However, it never distinguishes itself from near-neighbors such as zabbix_consultar_historico or zabbix_ultimos_valores, leaving an agent to guess why trends differ from history.

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?

'para períodos disponíveis' hints at a constraint but never states when to choose this over history/ultimos_valores, nor what makes a period 'available'. No exclusions or prerequisites are given.

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