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

With no annotations, the description carries the full burden. It discloses the mutating nature, the need for confirmation, the default workItemType, and the formatting of description into <p> tags. It does not cover error handling or permissions, but the disclosed behaviors are substantial and accurate.

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 three sentences with no redundancy. It front-loads the primary action and return value, then includes the confirmation warning, defaults, and parameter clarifications in a logical order. Every sentence earns its place.

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 no output schema, the description explains the return (id + browse URL). It covers defaults, project meaning, and description formatting. For a 5-parameter creation tool with 2 required, it is reasonably complete, though it could mention error scenarios or tag behavior, which are already in the schema.

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%, providing a baseline of 3. The description adds value beyond the schema by explaining the project arg (URL segment), description formatting, and the default workItemType, enhancing agent understanding of parameter usage.

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 clear verb and resource: 'Create a new AzDO work item.' It also mentions the return of id and browse URL. While it doesn't explicitly differentiate from sibling tools (azdo_get_work_item, azdo_search_work_items), the verb 'Create' makes the purpose unambiguous among the three AzDO tools.

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 provides clear context: it is a mutating operation requiring user confirmation, and it explains the default workItemType and the meaning of the project argument. However, it does not explicitly state when to use this tool versus the read-oriented siblings, though the create verb implies this distinction.

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