azdo_link_work_items

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

The description only says 'Link work items', which implies a write operation, but it does not disclose any behavioral traits such as whether existing links are affected, permission requirements, or reversibility. No annotations exist to compensate, leaving the agent with minimal insight.

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 (three words), which avoids verbosity but lacks sufficient substance. It is front-loaded but under-specified, earning a middle score for conciseness without adequate informativeness.

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?

The tool is moderately complex with five required parameters and no output schema. The description fails to explain what 'linking' means in Azure DevOps, what happens upon success, or any constraints. This leaves the agent underinformed for correct invocation.

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?

All five parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning. The baseline is 3, and the parameter descriptions are clear enough for understanding inputs.

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 'Link work items' clearly states the verb and resource, and the schema parameters (source_id, target_id, link_type) confirm the purpose of linking two items with a type. However, it could be more explicit about creating a relationship, but it's not ambiguous given sibling tool names.

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. There is no indication of when to use this tool versus alternatives like azdo_update_work_item (which might also manage links) or azdo_create_work_item. The agent receives no context for selection.

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