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

Annotations only declare readOnlyHint, so the description usefully adds that tiles are returned inline and that a preset Overview comes back with resolved: true and business-specific tiles. That is genuine behavioral context beyond the annotation, though the second sentence is compressed enough that an agent may not parse the resolved flag's meaning confidently.

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 short sentences with the read behavior front-loaded and no filler. The trailing clause about the Overview preset is dense but still earns its place by disclosing resolution behavior.

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?

There is no output schema, and the description covers the shape loosely (dashboard plus tiles, plus the resolved flag). It leaves out where to get a valid id and whether tile content is returned raw or evaluated — relevant given the many dashboard-tile 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?

Schema description coverage is 0% and the single id parameter has no description, only min/max length. The description implies the id identifies a dashboard, but it does not say whether it is an id, a slug, or a name, nor how to obtain one.

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?

"Read one dashboard with its tiles" gives a specific verb and resource, and the singular "one" distinguishes it from list_dashboards. It does not explicitly name evaluate_dashboard or get_business_overview as alternatives, so sibling differentiation is only implicit.

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 implied by "Read one dashboard" plus the required id, but there is no explicit statement of when to pick this over list_dashboards or evaluate_dashboard. A single clause like "use evaluate_dashboard to render values" would have lifted this.

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