zabbix_diagnosticar_ambiente

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

No annotations provided, so the description bears the full disclosure burden. It never states that the operation is read-only/non-mutating, that it fans out across many Zabbix APIs, how long it takes, or what permissions it requires. The breadth of scope is the only behavioral signal conveyed.

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 front-loaded sentence with no filler, but it carries a stray '100.' list-number artifact that is pure noise and suggests copy-paste from a doc, slightly undermining trust in the definition.

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 zero parameters and an output schema present, the description need not explain return values or inputs. However, for a broad, likely costly aggregate diagnostic with no annotations, it should at minimum declare it is a read-only operation and roughly what the diagnosis covers or costs.

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, so per the rubric the baseline is 4. Nothing in the schema needs elaboration and the description does not misrepresent any inputs.

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?

Specific verb ('Produzir um diagnóstico holístico 360°') plus the resource and the five domains it spans (conectividade, descoberta, coleta, alertas, saúde). The 'holístico 360°' framing implicitly distinguishes it from narrow siblings like zabbix_diagnosticar_coleta or zabbix_verificar_descoberta, but no sibling is named explicitly.

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?

No statement of when to use this versus the many narrow diagnostic tools (zabbix_diagnosticar_coleta, zabbix_validar_conexao, zabbix_verificar_descoberta, zabbix_consultar_estado_sistema). No prerequisites, no exclusions, no cost or latency warning for what is presumably an expensive all-domain sweep.

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