pbi_create_measure

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

The description mentions that the tool fails if the name already exists, which is a behavioral trait. However, no annotations are provided, and the description does not disclose other relevant behaviors like destructiveness, permissions, or side effects.

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 short sentence, which is concise but lacks structure. It does not front-load key information or separate sections, and it omits important details, making it less useful than a longer, structured description.

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?

With 5 parameters (3 required), no output schema, and no annotations, the description is insufficient. It does not explain return values, parameter dependencies, or usage context, leaving significant gaps for the AI agent to reliably invoke the tool.

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 0%. The description only mentions 'table' but does not explain the meaning, format, or constraints of parameters like dax, name, format, or display_folder. It adds no value beyond the schema's property names.

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 states the specific verb 'Create' and resource 'measure', and includes the failure condition 'Fails if the measure name already exists'. This clearly distinguishes it from siblings like update_measure or delete_measure.

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?

No guidance on when to use this tool vs alternatives. For example, it does not mention that if the measure name exists, one should use update_measure. No prerequisites or context are provided.

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