devops_work_item_delete

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

Annotations indicate readOnlyHint=false, meaning a write operation. The description adds key behavioral details: default sends to Recycle Bin, destroy=True is irreversible, requires specific permissions. No contradictions.

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?

Two sentences with critical information front-loaded. No fluff or redundancy. Warnings and alternatives are clearly expressed.

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 presence of an output schema (not shown but indicated) and 100% parameter coverage, the description fully explains the tool's behavior, permissions, and irreversible action. No gaps.

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%, but the description provides concise semantics for both parameters: work_item_id is the target, destroy controls behavior. The schema itself already details destroy's meaning, so the description adds moderate value.

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 explicitly states 'Delete a work item by ID', distinguishing between two behaviors (move to Recycle Bin vs. permanent destruction). This differentiates it from the sibling devops_work_item_undelete, which restores items.

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 explains when to use each mode (default recycle vs. permanent destroy) and mentions required permissions for destroy. It does not explicitly contrast with siblings, but the sibling context implies deletion vs. undeletion.

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