get_dashboard

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

No annotations are provided, so the description must disclose behavioral traits. It implicitly indicates a read operation but does not explicitly state that it is safe to call repeatedly, nor does it mention potential errors, authentication requirements, or impact on the system.

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 concise (two sections: Args and Returns) and front-loaded with the core purpose. It could be slightly more structured (e.g., bullet points for returns) but is efficient for a simple tool.

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 an output schema present, the description adequately summarizes return contents (cards, parameters, layout). However, missing usage guidelines and behavioral details leave gaps for a tool in a set of 21 siblings.

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 explains the single parameter dashboard_id as 'The ID of the dashboard,' adding meaningful context beyond the schema's type constraint (integer). This compensates for the 0% schema description coverage.

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's purpose: 'Get detailed information about a specific dashboard.' It uses a specific verb+resource combination and distinguishes itself from sibling tools like list_dashboards (list vs. get) and update_dashboard (update vs. read).

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that list_dashboards should be used for browsing dashboards before fetching details, nor does it specify any prerequisites or context for use.

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