pbi_bulk_create_measures

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

No annotations exist, so the description carries the full burden. It discloses a key behavior: 'The whole batch is validated before any write happens,' adding transparency about validation-before-write. However, it does not mention idempotency or error handling.

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?

Two sentences: first states purpose, second provides structure and behavioral note. No extraneous information, efficient and front-loaded.

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 one-parameter input and no output schema, the description covers what the tool does, required fields, and a key behavioral trait (validation before write). It lacks details on error handling, limits, or success response, but is reasonably complete for this simple 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?

With 0% schema description coverage, the description fully compensates by specifying the structure of the measures array: table, name, dax, optional format and display_folder. This provides critical meaning beyond the schema's empty items definition.

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 many measures at once,' specifying the verb (create), resource (measures), and bulk scope. It distinguishes from the sibling pbi_create_measure which handles a single 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?

The description implies usage when many measures need to be created at once, but lacks explicit guidance on when not to use it or alternatives (e.g., pbi_create_measure for single measures). No when-to-use vs. when-not statements.

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