openpanel_get_dashboard

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

No annotations provided, so description carries full burden. Adds valuable behavioral context by specifying 'including all charts', indicating the response contains nested chart data. However, missing read-only safety declaration, error behavior (404 handling), and performance characteristics.

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?

Brief single sentence, but the '[UNIFIED]' tag is structural noise that doesn't serve the agent. Core message is efficient, but the metadata leakage violates 'every sentence earns its place.'

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 3 required parameters (0% schema coverage), no annotations, and no output schema, the description is insufficient. Needs to explain parameter relationships (site+project_id+dashboard_id) or hint at return structure to guide invocation.

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% with no descriptions for site, project_id, or dashboard_id. Description fails to compensate, mentioning 'dashboard' loosely but providing no semantics for the three required parameters (e.g., what 'site' refers to, ID formats).

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?

Clear verb 'Get' and resource 'dashboard details including all charts'. The '[UNIFIED]' prefix is noise, but the core description effectively distinguishes this singular retrieval operation from sibling 'openpanel_list_dashboards' (plural list) and mutation tools like 'openpanel_create_dashboard'.

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 use this versus alternatives, prerequisites for the required IDs, or workflow (e.g., use list_dashboards first to discover dashboard_id). Simply states what the tool does without context for selection.

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