Create work item

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

With no annotations provided, the description carries the disclosure burden. It does disclose that this is a mutating operation requiring write tool access and a confirmation flag. However, it doesn't mention side effects like notifications, validateOnly behavior, or project defaulting, and the confirm requirement is already present in the schema.

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 short, front-loaded sentences with no filler. The action, resource, and key prerequisite are all stated efficiently.

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 12-parameter mutation tool with no annotations and no output schema, this description is too sparse. It omits return behavior, project defaults, notification defaults, and validateOnly semantics. The prerequisites help, but the overall specification is under-informative.

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 only 42%, so the description should compensate for undocumented parameters. It adds only the phrase 'standard or custom fields' and repeats the confirm requirement. It does not clarify tags, areaPath, assignedTo, iterationPath, description, or suppressNotifications.

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 states a specific action ('Create'), a concrete resource ('Azure Boards work item'), and a scope ('standard or custom fields'). This clearly distinguishes it from siblings like update_work_item, query_work_items, and add_work_item_comment.

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?

It clearly communicates when to use the tool: to create a work item, and it adds an important prerequisite ('Requires write tools and confirm=true'). It doesn't explicitly contrast with alternatives like update_work_item, but the creation context is unambiguous.

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