grafana_exportar_relatorio_pdf

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

No annotations are provided, so the description carries the full burden. It says 'PDF corporativo formatado' but never states whether a file is written to disk or returned, what happens if arquivo_saida is omitted, whether existing files are overwritten, or any size/pagination limits. For a file-generating tool with zero annotation coverage this is a significant gap.

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 efficient sentence with the action front-loaded, but the leading '79.' is meaningless filler and the brevity comes at the cost of substance rather than trimming redundancy.

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 5 parameters, 4 required, no annotations, and zero parameter documentation, the description is far too thin; it leaves the agent guessing about required inputs like resumo and the file output path, even though the output schema covers the return value.

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?

Five parameters with 0% schema description coverage: 'titulo', 'resumo', 'cabecalhos', 'linhas', 'arquivo_saida' are bare titles. The phrase 'dados e tabelas customizadas' loosely maps to linhas/cabecalhos, but it says nothing about resumo (a text abstract?) or how arquivo_saida defaults and behaves.

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 (Exportar) and resource (dados e tabelas customizadas -> documento PDF), which distinguishes it from the CSV/Excel sibling and the domain-specific report generators. However, the stray '79.' prefix is noise, and it doesn't clarify whether it is a generic table-to-PDF renderer versus a Grafana-native report export.

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 indication of when to use this over grafana_exportar_relatorio_csv_excel or the various grafana_gerar_relatorio_* tools. There are no prerequisites, exclusions, or alternative routing hints at all.

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