pbi_delete_measure

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

No annotations provided. Description merely states 'Delete a DAX measure' without warning about destructive nature, irreversibility, or cascading effects on visuals or relationships that depend on the measure.

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?

Very concise (one sentence) but overly terse. Misses opportunity to add value without sacrificing conciseness.

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?

For a simple delete tool with an output schema, description provides minimal context. Lacks info on return value, error conditions, or typical usage pattern.

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 has 0% description coverage. Description adds no meaning beyond property names. Agent must infer what 'name' and 'table' refer to, risking incorrect invocation.

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?

Description clearly states action ('Delete') and resource ('DAX measure'). However, it does not differentiate from sibling tools like pbi_delete_column or pbi_delete_table, which have similar patterns.

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 or when to prefer alternatives such as pbi_rename_measure or pbi_delete_column. No exclusion criteria or prerequisites mentioned.

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