pbi_create_relationship

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

With no annotations, the description discloses key behaviors: overwrite mode, action in response, and error raising. It lacks details on permissions or side effects, but covers core behavioral traits.

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 concise with front-loaded purpose, using two sentences. It could be more structured (e.g., bullet points for overwrite behavior), but it's efficient.

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 9 parameters with 0% schema coverage, the description should compensate but only covers one parameter. Output schema likely documents returns, but the description is insufficient for parameter understanding.

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 coverage is 0%, but the description only explains the 'overwrite' parameter. It does not clarify the meaning or constraints of other parameters like from_table, cardinality, direction, etc., which are critical for correct usage.

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 'Create or update a single-column relationship', which is a specific verb+resource. It clearly handles both create and update, distinguishing it from siblings like pbi_delete_relationship and pbi_list_relationships.

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 explains when to use overwrite=True vs False, and mentions the duplicate error. However, it doesn't explicitly compare with pbi_update_relationship, which could be an alternative.

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