List Lovelace dashboards

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully adds that it operates in both direct HA and VomeHome brokered mode, but says nothing about auth requirements, result limits, or the cross-home refusal behavior hinted at in the instance_id schema.

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 compact sentences with the resource and returned fields front-loaded and no wasted prose. The dual-mode sentence is the only slightly tangential element but is still informative.

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 compensates by naming the fields returned (url_path, title, mode, sidebar visibility), and the read-only nature is covered by annotations. For a simple list tool this is nearly complete; only edge behavior (cross-home refusal, limits) is left to the schema.

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 100% for the single instance_id parameter, so the schema already carries the semantics. The description adds no parameter-level detail beyond what the schema states, which is the expected baseline when the schema does the heavy lifting.

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 and resource (list Lovelace dashboards) and enumerates the returned fields (url_path, title, mode, sidebar visibility). It is distinguishable from the singular ha_get_dashboard sibling, though the description never explicitly contrasts them.

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 the verb 'List' versus the sibling get/create/save/delete tools, but there is no explicit when-to-use guidance or exclusion. The 'Works in direct HA mode and VomeHome brokered mode' note gives context but not a selection rule.

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