Build a dashboard by description (AI)

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

The description discloses important behavioral traits beyond annotations: it is a write operation (build and download .pbix), consumes AI credits, and polls for a few minutes. Annotations indicate readOnlyHint=false and openWorldHint=true, which align with the description. No contradiction.

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 concise with three sentences. The first sentence immediately states the core purpose, followed by usage requirements and behavioral notes. No redundant 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?

Given the tool's complexity (4 parameters, no output schema), the description covers all necessary aspects: purpose, required mutual exclusivity, credit consumption, polling duration, and output file. The agent has sufficient information to use the tool correctly.

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 descriptions, so baseline is 3. The description adds value by clarifying mutual exclusivity of 'solution' and 'sourceId', and by providing context for 'prompt' (describe in plain English) and 'outPath' (default path). This enhances understanding beyond the schema alone.

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 tool's purpose: building a dashboard via AI description and downloading the .pbix file. It specifies the verb 'build' and the resource 'dashboard', and distinguishes from sibling tools like daxops_build (likely a manual build) and daxops_delete_dashboard.

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 clear context: use when you want an AI agent to build a dashboard from plain English. It mentions the need to provide exactly one of 'solution' or 'sourceId', and notes that it consumes AI credits and polls to completion. However, it does not explicitly state when not to use this tool or suggest alternatives.

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