model_delete_relationship

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

The description is minimal and does not disclose behavioral traits beyond the obvious delete action. With no annotations, the description carries the full burden, but it omits side effects (e.g., cascading effects on measures or visuals), reversibility, or the behavior of the 'dryRun' parameter.

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 extremely concise (4 words), which is good for front-loading, but it sacrifices necessary detail. It lacks structure for readability and does not expand on critical aspects, making it borderline insufficient.

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 absence of an output schema and annotations, and the presence of 3 parameters (including an unexplained boolean), the description is incomplete. It does not describe return values, error conditions, or success criteria, leaving the agent with significant uncertainty.

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 to the parameters. While 'projectPath' and 'relationshipName' are self-explanatory from their names, the 'dryRun' boolean is not explained, leaving ambiguity about its effect (e.g., preview vs. actual deletion).

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 (relationship) with a specifying modifier (by name). It distinguishes itself from sibling tools like model_add_relationship or model_delete_measure, though it could be more explicit about what 'relationship' means in this context.

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 is provided on when to use this tool versus alternatives, such as when a relationship should be deleted versus updated. There is no mention of prerequisites (e.g., relationship must exist) or conditions that would make deletion inappropriate.

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