get_dashboard_panels

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

No annotations present, so description carries the burden. It discloses that it returns simplified panel info without full query definitions, and that it exists to avoid size limits. It does not explicitly mention read-only or auth, but as a 'get' operation it implies no side effects.

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?

Two sentences, starts with purpose, then usage note, then output. No fluff.

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?

Covers what, why, and parameter meanings. Output is described as JSON string with list of panels. Sufficient for a simple tool.

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?

The description provides short explanations for both connection_name and dashboard_uid, adding meaning beyond the schema which has no descriptions.

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 the action clearly (get simplified panel information) and identifies the resource (dashboard). It also distinguishes from alternative get_dashboard() by mentioning size limits.

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?

Explicitly advises using this tool for large dashboards to avoid MCP size limits, and implies get_dashboard() for other cases.

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