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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), so the bar is lower. The description still adds real behavioral context beyond them: the result contains per-tile names and data truncated to the first 50 rows, which warns the agent about output volume/capping.

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?

A single sentence that front-loads the action and resource and then supplies the return-content detail with zero filler.

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 no output schema, the description usefully documents what comes back and the 50-row-per-tile cap, which is the main thing an agent needs. It is slightly incomplete on nested tile metadata (chart types, formatting) and permission behavior, but adequate for the tool's complexity.

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?

Only one parameter with 100% schema description coverage ('Dashboard id or slug'), so the schema carries the semantics. The description adds nothing about the parameter itself, making the baseline 3 appropriate.

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 a specific verb (open/view) and resource (dashboard), plus the content returned: each tile's name and current data. It is distinguishable from sibling list_dashboards (catalog listing vs. rendering one dashboard), though it never says so explicitly.

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?

Usage is only implied — the agent can infer it opens one dashboard given an id/slug, but there is no explicit when-to-use guidance nor any statement contrasting it with list_dashboards or other viewer siblings like open_record.

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