deleteWorkItemsRelationship

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Deletes', implying destructiveness, but lacks details on prerequisites, error handling, partial success behavior, or whether the operation is reversible. This is insufficient for an agent to invoke safely.

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 one short sentence, which is concise, but lacks structured information like when, why, or how. It earns its place but does not front-load critical details. An ideal description would add context while staying brief.

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 complexity (4 required params, nested requestBody, and many siblings), the description is incomplete. It does not explain the returned value (no output schema) or the scope of relationships it can delete. The batch nature and importance of the requestBody data are underexplained.

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 descriptions for all parameters. However, the nested requestBody description ('The Relationship body.') adds little meaning beyond the schema. The enum for type is present but not explained in the description, so it provides no extra semantic value. Baseline of 3 is appropriate.

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 tool deletes Work Item Relationships, which is a specific verb+resource. It distinguishes from sibling tools like deleteLinkedWorkItem or deletePlanRelationship by targeting work item relationships generically, but could be more precise about the range of relationship types (as seen in the enum) to enhance differentiation.

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 provides no guidance on when to use this tool versus alternatives such as deleteLinkedWorkItem or deleteExternallyLinkedWorkItem. Given the large set of sibling delete tools, explicit usage context is missing, making it harder for an agent to select appropriately.

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