pbi_execute_dax

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

With no annotations, the description must fully disclose behavioral traits. It fails to mention whether the query is read-only, what side effects occur, authentication needs, or rate limits. The tool name implies execution, but the description lacks critical safety and behavior details.

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 a single sentence, which is concise but underspecified for a tool with multiple parameters. It sacrifices clarity and completeness for brevity, failing to earn its place by providing substance beyond the tool name.

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?

Despite having an output schema, the description does not explain what the tool returns (e.g., tabular results). It lacks completeness for a query execution tool: no mention of error handling, expected output format, or usage context, leaving 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?

Schema coverage is 0%, and the description adds no information about the three parameters (query, max_rows, timeout_seconds). The agent receives no explanation of their purpose, format, or constraints, making it difficult to use correctly.

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 ('Execute') and the resource ('DAX or DMV query'), which is specific and distinguishes it from many sibling tools focused on creation or validation. However, it does not explicitly differentiate from similar tools like pbi_execute_dax_as_role.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no context for typical use cases. Sibling tools such as pbi_validate_dax or pbi_execute_dax_as_role are not mentioned, leaving the agent without decision-making support.

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