Build a dashboard (.pbix)

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

Annotations indicate mutation (readOnlyHint=false) and side effects (openWorldHint=true). The description adds useful behavioral context: long-running operation ('polls to completion, can take a couple of minutes') and that it downloads to disk. 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?

The description is three sentences, front-loaded with the core purpose, then covers constraints and optional behavior. Every sentence adds essential information without redundancy or fluff.

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 8 parameters and no output schema, the description adequately covers the build process, polling, and download. It explains how to specify source, pages, and defaults. However, it lacks explicit mention of return values (e.g., success/failure, file path) and error handling, which would improve completeness.

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 coverage is 100% with all parameters described. The description adds value beyond the schema by specifying the exclusivity constraint (exactly one of sourceId or solution) and the default behavior for pages. This provides additional semantic guidance not present in 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 verb 'Build' and the resource 'Power BI .pbix dashboard'. It distinguishes from siblings like daxops_ai_build and daxops_list_* by specifying the build process with sourceId or Solution starter. The mention of polling and download adds specificity.

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 gives explicit constraints: 'Provide exactly one of sourceId or solution' and explains default behavior for pages. However, it does not provide guidance on when to use this tool versus alternatives like daxops_ai_build, nor does it state when not to use it.

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