delete_work_item_relation_definition

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only says 'Delete' without mentioning permanence, cascading effects, permission requirements, or error handling. For a destructive operation, this is a notable gap.

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, with a clear primary sentence and a single-line argument explanation. Every word is purposeful, no filler or redundant content.

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?

For a single-parameter delete tool, the description gives the essential purpose and parameter meaning. However, it lacks contextual detail about consequences (e.g., whether the deletion is permanent or cascades to related items) which is important for a destructive action. Notable gaps given no annotations or output schema.

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?

The description adds crucial meaning beyond the raw schema by stating the parameter is a 'UUID of the relation definition to delete'. Since the schema provides no description, this supplementary information explains the parameter's purpose and format, effectively compensating for the 0% schema coverage.

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 the resource ('workspace relation definition'). It distinguishes itself from related sibling tools like 'delete_work_item_link' and 'create_work_item_relation_definition' by explicitly naming the resource type.

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 a clear context: deleting a workspace relation definition. It implies the tool's specific use case without explicitly stating alternatives, but the name and sibling list make it evident. There is no exclusion like 'use delete_work_item_link for links', but the context is unambiguous enough.

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