dashboards_list_dashboards

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

No annotations are provided, so the description carries the full burden of behavioral transparency. While 'List' inherently suggests a read-only operation, the description does not explicitly state that the tool is safe, non-destructive, or whether it requires any permissions. It also does not mention potential rate limits or the behavior when no dashboards exist.

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 a single sentence with only four words: 'List all Lovelace dashboards.' It is extremely concise, front-loaded, and contains zero filler. Every word is essential to convey the purpose.

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?

For a simple list tool with no parameters and an existing output schema, the description adequately states that it returns all Lovelace dashboards. It could be slightly improved by hinting at the output structure (e.g., 'returns a list of dashboard IDs and names'), but given the simplicity and the presence of an output schema, it is largely complete.

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 tool has zero parameters and the schema description coverage is 100% (since no params exist). The description adds no parameter-specific meaning because there are none. Baseline score of 3 is appropriate as the schema already fully covers the parameter aspect.

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 'List all Lovelace dashboards' uses a specific verb 'List' and resource 'Lovelace dashboards', clearly distinguishing it from siblings like dashboards_get_dashboard_config (which retrieves a single dashboard's config) or dashboards_add_card_to_view (which modifies a dashboard). The purpose is explicit and unambiguous.

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 implies this tool is for retrieving all dashboards, but it does not provide explicit guidance on when to use it versus alternatives, nor does it specify when not to use it. No exclusions or alternative tool names are mentioned. The context is implied but lacks explicit direction.

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