Create Dashboard

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

Annotations already indicate non-readOnly and non-destructive. The description adds behavioral context by explaining widget creation flow, grid layout constraints, and that the tool returns the created dashboard object with new ID. No contradictions with annotations.

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?

Well-structured with bullet points for widget types and grid layout. Front-loaded with main purpose. Efficient but somewhat lengthy due to detailed widget explanations; every sentence serves a purpose.

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?

Covers essential aspects: widget types, grid layout, references to sibling tools, and return value. Lacks error handling or prerequisites information, but for a creation tool with rich annotations, it is fairly complete.

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%, but the description adds significant value beyond schema by explaining widget types with examples, grid layout (max 12), and referencing appd_browse_metric_tree. It clarifies optionality and provides usage patterns not in 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 clearly states 'Create a new custom dashboard in AppDynamics' with specific verb (create) and resource (dashboard). It distinguishes from sibling tools like appd_add_widget_to_dashboard and appd_auto_build_dashboard by explaining how to provide widgets upfront or create a blank dashboard for later addition.

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 clear guidance on when to use this tool (to create a dashboard) and mentions alternatives (use appd_add_widget_to_dashboard for adding widgets later, appd_browse_metric_tree for metric paths). Lacks explicit 'when not to use' statements, but differentiation from siblings is effective.

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