pbi_delete_relationship

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

With no annotations, the description carries full burden but only states 'Delete a relationship', missing details on irreversible changes, dependencies, or required model refreshes. The minimal disclosure leaves behavioral traits largely unspecified.

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?

A single sentence efficiently communicates the action and methods with no superfluous content, making it immediately scannable and information-dense.

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 existence of an output schema and the simplicity of a delete operation, the description provides sufficient context for the tool's basic use. It covers the core functionality, though additional notes on side effects would improve completeness.

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?

Despite 0% schema description coverage, the description groups parameters into two approaches ('by name' vs 'by endpoint columns'), adding meaningful structure beyond the raw schema. It clarifies semantic usage without detailing each parameter individually.

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 uses a specific verb ('Delete') and resource ('relationship'), and specifies two distinct methods ('by name or by endpoint columns'), clearly distinguishing it from sibling tools like pbi_create_relationship or pbi_update_relationship.

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?

It states when to use this tool (to delete a relationship) and provides two methods, but does not explicitly mention when not to use it or list alternatives like editing via pbi_update_relationship. This is clear but lacks exclusionary context.

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