create_dashboard

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

The description only states the creation action without disclosing any behavioral traits such as side effects, permissions required, or what happens to existing dashboards. With no annotations provided, the description fails to warn about potential impacts.

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 extremely concise at only three words, which avoids verbosity. However, it could be more informative without sacrificing conciseness, such as adding a brief note about required fields or typical usage.

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 lack of annotations and output schema, the description should provide more context about the dashboard creation process, such as whether it triggers any events or if the dashboard is immediately available. The minimal description leaves significant gaps.

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 input schema has 100% coverage with a description for the 'body' parameter, but the tool description adds no additional meaning. The nested properties 'name' and 'order' are undocumented in the description, so it relies entirely on the schema. Score is baseline due to high schema coverage.

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 clearly states the action (create) and resource (dashboard instance), making the primary purpose unambiguous. However, it does not differentiate from sibling tools like 'create_widget' or 'update_dashboard', which could lead to confusion about when to use which.

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. There is no mention of prerequisites, conditions, or exclusions, leaving the agent without context for appropriate invocation.

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