ado_work_item_create

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It reveals only that this is a creation action gated by write mode, but it does not disclose permissions, side effects, prerequisites beyond write mode, or failure behavior.

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, front-loaded sentence with no filler, so it is efficient. It is appropriately concise, though its brevity creates substantive gaps already scored elsewhere.

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 has a nested request schema and no annotations, and the description only covers the write-mode precondition. It does not clarify required field semantics, project defaulting, or expected behavior, so an agent is left to infer too much. The presence of an output schema reduces the need for return-value detail but does not fill the other 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 description coverage is 0%, so the description needed to explain the request object, required title and work_item_type, and optional fields/project/description; it mentions none of them. The schema names fields but provides no descriptions, so the burden is unmet.

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 and resource, 'Create a work item,' which clearly identifies the operation. It does not explicitly distinguish itself from the sibling ado_work_item_update tool, so it stops short of full sibling differentiation.

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 phrase 'when write mode is enabled' provides a concrete precondition, so an agent knows this tool is not available for read-only calls. However, it gives no alternative routing or when-not guidance, leaving the choice between create and update mostly to inference from the tool name.

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