deleteExternallyLinkedWorkItem

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

No annotations are provided, and the description only states the action (deletes). It lacks disclosure of side effects, permanence, or required permissions. For a delete operation, behavioral context is critical.

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 a single short sentence, but it is under-specified. Conciseness is not a virtue when critical information is missing. The structure is too minimal for a tool with six required parameters.

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 (6 required params, many siblings, no output schema or annotations), the description is severely incomplete. It does not explain return values, side effects, or when to use this tool over similar ones.

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%, so each parameter has a basic description. The tool description adds no additional meaning beyond what the schema provides. Parameters like 'roleId' and 'hostname' could benefit from context, but the schema already gives minimal 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 uses a specific verb ('Deletes') and resource ('Externally Linked Work Item'), clearly indicating the action. However, it does not distinguish from siblings like 'deleteLinkedWorkItem' or 'deleteExternallyLinkedWorkItems', which could cause confusion.

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?

No usage guidance is provided. The description does not specify when to use this tool versus alternatives, such as when to delete a single externally linked item vs multiple, nor any prerequisites or context.

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