pbi_delete_column

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

Without annotations, the description must disclose behavioral traits. It only states 'Delete', implying destructiveness, but fails to mention whether deletion is permanent, checks dependencies, requires specific permissions, or affects related objects. This is a significant gap for a mutation tool.

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 very short (6 words), which is concise, but it prioritizes brevity over completeness. It lacks necessary context, so it does not fully earn its place; a slightly longer description with key behavioral details would improve utility.

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 tool's simplicity (2 parameters, no annotations, output schema exists), the description should cover dependencies, error cases, and return value. It fails to do so, leaving the agent underinformed. An output schema is present but unacknowledged.

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%, yet the description adds no meaning for the two required parameters (name, table). It does not explain what values are acceptable, formats, or constraints, leaving the agent to infer solely from parameter 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 clearly states the action (delete) and resource (a column from a table), distinguishing it from sibling tools like pbi_delete_table or pbi_delete_measure. However, it does not explicitly differentiate from similar column operations, but the verb and object are specific.

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 versus alternatives, such as pbi_rename_column or pbi_set_column_data_type. The description does not specify prerequisites, when not to use (e.g., column used in measures/relationships), or consequences.

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