deletePlanRelationship

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

With no annotations provided, the description must fully convey behavioral traits. It only states removal but omits critical details like required permissions, whether the operation is destructive, or any side effects (e.g., cascading deletes). The description adds minimal value beyond the tool name.

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 concise at one sentence, but it essentially restates the tool name. While brevity is good, the description sacrifices helpfulness for conciseness. It could provide more context without becoming verbose.

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 complexity of the requestBody parameter and the lack of an output schema, the description is incomplete. It does not explain the relationship types in the data array, the purpose of the requestBody, or what the tool returns. More detail is needed for an agent to use it correctly.

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 100% with parameter descriptions provided. The tool description does not add extra meaning beyond the schema, such as explaining how the requestBody should be structured or how relationshipId relates to the data array. Baseline score of 3 is appropriate as schema already covers parameters.

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 ('Removes') and the resource ('specific Relationship from the Plan'). It distinguishes this tool from siblings like deletePlan (removes a plan) or deleteWorkItemsRelationship (removes work item relationships), making the purpose unambiguous.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives like patchPlanRelationships or other delete tools. An agent would need to infer usage context from the name alone, which is insufficient for complex scenarios.

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