ha_create_dashboard

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

The description lacks any behavioral traits: it does not mention that creating a dashboard may overwrite existing ones, that admin access can be enforced, or that it defaults to showing in sidebar. With no annotations to compensate, the agent gets no safety or side-effect information.

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 concise sentence that serves its purpose, but it lacks structure and detail. It is not overly verbose, yet it could be more informative without sacrificing brevity.

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?

Given the complexity of 5 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain return values, error handling, idempotency, or any side effects, leaving the agent with insufficient context to use the tool reliably.

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?

All 5 parameters are fully described in the schema (100% coverage), so the description adds no additional meaning beyond what the schema provides. Baseline score of 3 is 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?

The description 'Create a new Lovelace dashboard' uses a specific verb ('create') and resource ('Lovelace dashboard'), clearly distinguishing it from sibling tools like ha_delete_dashboard, ha_update_dashboard, and ha_list_dashboards.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., ha_create_dashboard_config), nor any prerequisites or exclusions such as uniqueness of url_path or required permissions.

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