List Lovelace dashboards

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

Annotations cover safety (readOnly, idempotent, non-destructive), and beyond that the description discloses that the default dashboard is excluded because it has no url_path. That is a non-obvious exclusion an agent must know to avoid a false negative.

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?

Front-loaded verb statement, then API call, then fields, then a labeled 'Use when' and 'Returns' clause. Every sentence carries information; no padding.

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?

Complete for a zero-param list tool: purpose, API endpoint, return fields, the one important edge case (default dashboard excluded), and routing to downstream tools. Output schema covers return values; nothing material is missing.

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?

Zero parameters, so per the rubric the baseline is 4. The description also documents the return shape (id, url_path, title, mode values) which is useful even though an output schema exists.

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+resource ('List every registered Lovelace dashboard') and even names the underlying API call. Distinguished from siblings by scoping to dashboards, not entities/areas/etc.

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?

Explicit when-to-use: 'discovering a dashboard's url_path before calling dashboards_get_dashboard_config or dashboards_screenshot.' Names the exact downstream tools and the precondition, leaving nothing to inference.

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