ado_delete_work_item

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

With no annotations, the description carries full burden. It discloses the default logical deletion behavior and the option for permanent deletion via destroy=true, adding behavioral context beyond the schema. However, it does not mention side effects, recovery options, or required permissions.

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 concise sentences with no wasted words. Each sentence provides essential information: the action and the key behavioral nuance (logical vs permanent deletion).

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 deletion tool with no output schema, the description covers the main behavior and parameter distinction. Missing info on required confirm parameter (though schema states it) and error conditions, but overall sufficiently complete for the core operation.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining the destroy parameter's purpose and the default deletion mode, clarifying behavior beyond the schema's property descriptions.

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 'Elimina un Work Item' and the resource (Azure DevOps Work Item). It distinguishes between logical and permanent deletion, providing specificity beyond mere deletion.

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 the destroy parameter for permanent deletion versus default logical deletion, but does not provide explicit guidance on when to use this tool versus sibling tools (e.g., other delete operations) or conditions to avoid using it.

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