grafana_consultar_influxdb

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

No annotations exist, so the description carries the full burden. 'Consultar' implies a read operation, and 'através do proxy do Grafana' adds a bit of architectural context, but nothing is said about permissions, whether the datasource must exist, rate/size limits on queries, or pagination. An output schema exists, so return formatting need not be covered, but the operational behavior remains undeclared.

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 padding. The leading '35.' ordering artifact is noise that does not serve the agent, but the sentence itself is efficient.

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 query-execution tool with zero annotation coverage and 0% schema description coverage across four parameters, one sentence is insufficient. The agent is left to guess the datasource_uid sourcing and the accepted time-range syntax, which are the main failure modes for this call.

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 coverage is 0% and four parameters are undocumented. The description only hints that 'consulta' should be a Flux or InfluxQL query; it says nothing about 'datasource_uid' (how to obtain a valid one), 'de'/'ate' (defaults now-1h/now are visible in schema but the accepted time-expression format is not explained).

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 (Consultar) and resource (métricas no InfluxDB) and even names the two supported query languages (Flux or InfluxQL) plus the access path (proxy do Grafana). It implicitly separates itself from influxdb-adjacent siblings like grafana_consultar_prometheus/loki, but never names them 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?

There is no statement of when to use this tool versus grafana_executar_consulta, grafana_consultar_prometheus, or grafana_consultar_fonte_sql. The InfluxDB reference implies the context, but no alternatives, prerequisites, or exclusions are given.

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