get_dashboard

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

With no annotations, the description carries the burden. It states the tool is a retrieval (read) operation and returns 'Dashboard details including all cards', but does not disclose any behavioral traits like authorization needs, side effects, or data freshness. Adequate but minimal.

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?

The description is short, with a clear one-line purpose, followed by Args and Returns sections. Every sentence serves a purpose without redundancy or 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?

Given the tool's simplicity and the presence of an output schema (not shown but implied), the description sufficiently explains the tool's scope (specific dashboard, including cards). However, it could better differentiate from get_dashboard_cards and note any limitations (e.g., no pagination info).

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%, so the description's 'dashboard_id: The ID of the dashboard' provides basic human-readable meaning. However, it adds no format, source, or validation hints beyond the schema's type declaration.

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 description clearly states the tool retrieves detailed information for a specific dashboard (verb 'Get' + resource 'dashboard'), distinguishing it from sibling tools like list_dashboards (which lists) or get_dashboard_cards (which focuses on cards).

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 tool versus alternatives (e.g., get_dashboard_cards, search_dashboards). The description does not mention context, prerequisites, or exclusions, leaving the agent to infer from tool names.

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