grafana_obter_resumo_dashboard

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 discloses one behavioral trait — trimmed output to avoid oversized JSON — which is useful, but says nothing about read-only nature, permissions, or what metadata is included versus omitted.

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?

One short sentence with no padding, but the stray "3." numbering prefix wastes the front-loaded position and signals copy-paste from an external list rather than a deliberate 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?

An output schema exists, so return values need not be explained, and the trimmed-output note sets size expectations. However, the missing uid semantics and absent sibling routing leave gaps an agent would need to close elsewhere.

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?

There is a single required `uid` parameter with 0% schema description coverage, and the description never explains that uid identifies the dashboard. With the schema silent, the description should compensate but does not.

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 verb "Recuperar" plus the resource "metadados e lista resumida de painéis" gives a rough sense of the action, but the object is ambiguous: it never says the summary is for a dashboard identified by uid, and the leading "3." is a leftover list artifact. It gestures at a lighter alternative to full dashboard retrieval without naming the sibling it replaces.

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?

"sem retornar JSON excessivo" hints that this is the lightweight option, but no sibling (e.g. grafana_obter_dashboard) is named and no explicit when-to-use/when-not condition is given. An agent must infer the choice from the name alone.

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