grafana_consultar_prometheus

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether the call is read-only, what permissions or datasource_uid resolution rules apply, timeouts, or result-size limits. It adds no context beyond the tool name.

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 wasted clauses, but it opens with a stray '32.' list-numbering artifact and is terse to the point of being under-specified rather than concise.

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?

For a 5-parameter, unannotated query tool, the description leaves the agent without enough to call it correctly: how to switch between instant and range mode, what datasource_uid does when null, and what range/step defaults mean. The output schema covers return values, but the input side is severely under-described.

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 5 parameters, so the description must compensate and does not: de/ate (time range with defaults now-1h and now), passo_segundos (step), and datasource_uid (datasource selection vs default) are never explained. Only the promql parameter is implicitly covered by 'consulta PromQL'.

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 + resource: executes a PromQL query against a Prometheus datasource, with the instant/range distinction stated. It is clearly not a Loki, Tempo, or InfluxDB query, but it does not explicitly position itself against the generic sibling grafana_executar_consulta.

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 guidance on when to choose this over grafana_executar_consulta (generic query execution) or the other backend-specific consultar_* tools, and no prerequisites or exclusions. The 'instantânea ou de intervalo' phrase hints at mode but never says which parameters select it.

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