ado_create_items

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals non-obvious behaviors: automatic assignment to the configured Area Path, sprint assignment via parameter, and hierarchy creation. It does not mention permissions or failure modes, but the disclosed behaviors are significant beyond 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?

The description is two sentences, starting with the core purpose and followed by key behavioral details. Every word earns its place, with no filler or repetition of schema information.

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 structure and no output schema, so completeness depends on the description. It covers hierarchy, area path, and sprint, but misses mentioning Bug in the hierarchy and lacks any note about prerequisites (e.g., ado_configure) or return values. This leaves some gaps for a complex tool.

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 100%, so the baseline is 3. The description adds value by explaining the effect of addToCurrentSprint and the Area Path behavior, which goes beyond merely listing parameters. However, the hierarchy description omits the 'Bug' type present in the schema, slightly reducing clarity.

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 starts with a specific verb and resource: 'Create work items in Azure DevOps'. It also mentions a unique capability: 'optional hierarchy (Epic > Feature > User Story > Task)'. This clearly distinguishes it from sibling tools like update_item or delete_item, establishing a precise purpose.

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 clearly indicates the tool's function and provides contextual guidance such as 'Items are assigned to the configured Area Path' and 'Use addToCurrentSprint=true to add items to the active sprint'. While it doesn't explicitly mention alternatives or exclusions, the usage context is clear and implies this is for creating new items.

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