azdo_create_work_item

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. 'Create work item' implies a write/mutation operation but doesn't disclose authentication requirements, rate limits, what happens on success/failure, whether the creation is immediate or queued, or what permissions are needed. For a tool with 24 parameters that creates database records, this is critically insufficient.

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 maximally concise at just two words. While this represents under-specification rather than ideal conciseness, according to the scoring rules, 'under-specification' should not penalize conciseness. The description has zero wasted words and is front-loaded with the core action.

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 complex creation tool with 24 parameters, no annotations, no output schema, and multiple sibling tools, the description is completely inadequate. It doesn't explain what gets created, how to use it alongside other tools, what the response looks like, or any behavioral characteristics. The 100% schema coverage helps with parameters but doesn't compensate for the missing higher-level context.

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?

The description adds no parameter information beyond what's already in the schema. However, with 100% schema description coverage where every parameter has a clear description, the baseline score is 3. The description doesn't compensate for any gaps because there are none in the schema, but it also doesn't add value by explaining relationships between parameters or providing usage examples.

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 'Create work item' is a tautology that restates the tool name without adding meaningful context. It doesn't specify what kind of work item (Azure DevOps work item) or distinguish it from sibling tools like 'azdo_update_work_item' or 'azdo_link_work_items'. While the verb 'create' is clear, the resource 'work item' lacks specificity given the Azure DevOps context.

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 zero guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when to use this versus 'azdo_update_work_item', or any context about required permissions or setup. Given the complex sibling toolset with multiple work item-related tools, this lack of guidance is particularly problematic.

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