create_dashboard

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

No annotations are present, so the description carries the full behavioral burden. It discloses that creation is storage-mode, the dashboard is immediately visible, it starts empty, and the URL pattern. It omits important mutation details such as duplicate url_path handling, required permissions beyond the parameter, and return behavior.

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-loads the purpose, then adds two useful behavioral sentences, then a clean Args block. Every sentence and parameter entry serves a clear purpose with no wasted text.

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 a 5-param creation tool with no annotations and no output schema, the description covers purpose, URL behavior, empty-start state, and all parameters. It could optionally mention duplicate handling or permission requirements, but is largely complete for correct invocation.

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%, so the description must compensate. It gives meaningful semantics for all five parameters, including concrete examples for url_path ('moestuin' yields /lovelace-moestuin) and icon ('mdi:sprout'), and clarifies title, show_in_sidebar, and require_admin.

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 ('Create a new storage-mode Lovelace dashboard') and adds immediate visibility and empty-start behavior. It distinguishes itself from sibling dashboard tools like update_dashboard_metadata and set_dashboard_config by being the creation operation.

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?

Provides implied usage by noting the dashboard starts empty and that views and cards must be added separately, steering the agent to append/replace view and card tools afterward. However, it does not explicitly state when to use this versus update_dashboard_metadata or set_dashboard_config, nor does it list exclusions.

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