delete_work_item_relation_definition

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds no additional behavioral context, such as whether deletion cascades or if underlying relations must be empty first. It simply restates the name's action.

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: two sentences with no fluff. The verb-resource pattern is front-loaded, and the parameter is documented efficiently. Every word earns its place.

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 low complexity (single parameter, no output schema), the description covers the basics but leaves gaps. For a destructive and idempotent tool, it does not address side effects or prerequisites (e.g., whether the definition must be unused). It is adequate but not thorough.

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?

With 0% schema description coverage, the description must compensate. It documents the parameter 'definition_id' as 'UUID of the relation definition to delete,' adding purpose beyond the schema. However, it omits format specifics or constraints beyond the term 'UUID', leaving some ambiguity.

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'), leaving no ambiguity. It effectively distinguishes the tool from siblings like create, update, and list.

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 implies usage when deletion of a relation definition is needed, but provides no explicit guidance on when to use versus alternatives, no prerequisites, and no exclusions. For a destructive tool, context about requirements (e.g., no existing relations) would be helpful.

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