zabbix_exportar_relatorio_pdf

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

With no annotations provided, the description carries the full behavioral burden and does not meet it: it never says whether a file is written to disk, where the artifact lands, whether an existing file is overwritten, or what permissions are required. The only behavioral hint (that the PDF contains header, period, tables and conclusions) is useful but does not cover side effects or failure modes.

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 is appropriately sized, but the leading "48." ordinal is meaningless noise that adds no informational value to the agent.

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?

The output schema means return values need not be described, but for a no-annotation, file-producing mutation with three parameters at 0% schema coverage, the description is too thin. It omits valid report types, file destination/overwrite behavior, and relative ranking versus the Excel export and scheduling siblings.

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 the description must compensate, and it only partially does: "período" loosely maps to periodo_dias, but nome_arquivo (is it a path? relative or absolute? overwrite semantics?) and tipo_relatorio (what values are accepted beyond the default "executivo"?) are left unexplained in both schema and description.

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 pairs a specific verb ("Gerar") with a specific artifact ("documento PDF corporativo") and even enumerates its sections (header, period, tables, conclusions), so an agent knows what the tool produces. It does not, however, distinguish itself from the crowded sibling set of report generators or from zabbix_exportar_relatorio_excel, which is the nearest alternative.

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 this tool should be chosen over zabbix_gerar_relatorio_* or zabbix_exportar_relatorio_excel, and no prerequisites such as having generated a report first or having write access to a target directory. The agent must infer usage entirely from the tool name.

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