create_new_dashboard

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

With annotations already indicating readOnlyHint=false and idempotentHint=false, the description adds context by explaining the two layout types ('ordered' and 'free') and pointing to the datadog://widget-templates resource for widget definitions. This goes beyond what annotations provide, though it doesn't elaborate on side effects or error handling, which are partially covered by the presence of an output schema.

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 compact and well-structured: a single opening sentence, a usage condition, a resource pointer, and two bullet points for layout types. Every sentence adds value, and the key information is front-loaded.

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 tool's complexity (7 parameters, 3 required), the description covers the essential context: when to use it, how to structure layouts, and where to find widget templates. The remaining parameters are fully described in the schema, so no further description is needed. The presence of an output schema also covers return-value expectations.

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 100%, so the schema already describes every parameter. The tool description adds extra meaning for layout_type by explaining what 'ordered' and 'free' mean, and for widgets by referencing a resource with ready-to-use definitions. This is valuable enrichment beyond the schema.

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 opens with 'Create a new dashboard with custom widgets and layout,' which uses a specific verb and resource, clearly distinguishing it from sibling tools like update_existing_dashboard, get_dashboard_details, and list_all_dashboards. The mention of 'custom widgets and layout' further clarifies its scope.

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 explicitly states 'Use this when: user wants to visualize metrics, create a monitoring view, or track KPIs,' providing clear context for when the tool is appropriate. It does not explicitly mention exclusions or contrast with alternatives like update_existing_dashboard, but the use-case guidance is strong enough to guide selection.

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