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

No annotations are provided, so the description carries the full burden. It explicitly flags itself as a mutating operation requiring user confirmation, which is exactly the disclosure needed. It also discloses HTML wrapping behavior for description and the project name subtlety (often same as URL segment after org). Slight gap: no mention of failure modes or permission requirements, but key mutating-warning is stated directly.

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?

Compact and informative — five sentences covering purpose, return value, safety warning, and the most important param nuances. Slightly dense but every sentence earns its place. None of it is redundant with the schema.

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?

No output schema, so the description compensates by naming the return (id + browse URL). With 5 parameters and 100% schema coverage, plus key behavioral warnings (confirm-first, HTML wrapping, project name quirk), the description provides solid context for a moderately-complex create tool. Would benefit from a mention of error output format, but coverage is strong overall.

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%, so the schema already documents all 5 parameters. The description adds genuine value beyond the schema: clarifies the project arg matches the URL segment after the org, notes description gets wrapped in <p> tags, and explains tags are stored as semicolon-separated internally. These are non-obvious behaviors the schema doesn't convey.

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?

Description clearly states verb+resource ('Create a new AzDO work item') and explicitly notes it returns the new id + browse URL. Distinguishes cleanly from siblings azdo_get_work_item and azdo_search_work_items via the create semantics.

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?

Explicitly instructs 'ALWAYS confirm with the user before calling' with the reason listed (mutating operation). The 'project' clarification and default workItemType guidance give concrete context on when/how to invoke. Strong behavioral guardrails present.

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