List built-in dashboard templates

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

Declared as 'Read-only enumeration', making the non-destructive nature clear. Also lists returned fields (id, name, tagline, description, icon, widget_count) so the agent knows exactly what to expect.

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 concise sentences, front-loaded with the core purpose and no unnecessary words. Every sentence provides actionable information.

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?

Despite no output schema, the description sufficiently enumerates return fields. Contextual guidance on next steps (dashboard_template_get) completes the picture for an agent.

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?

No parameters in the input schema (schema coverage 100%), so no parameter info to add. Baseline score of 3 is appropriate; description does not detract but also cannot add value for parameters.

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 explicitly states the purpose: 'Read-only enumeration of every starter dashboard the platform ships with.' It clearly distinguishes this listing tool from sibling tools like dashboard_template_get and dashboard_create by mentioning usage flow.

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 provides explicit when-to-use guidance: 'Use dashboard_template_get(id) to retrieve the full widget specs, then materialize via dashboard_create + widget_create calls.' This tells the agent how to chain this tool with others for a complete workflow.

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