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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: it returns the new id and browse URL, defaults workItemType, and states that plain text gets wrapped in <p> tags. This is useful context beyond the structured fields, though it doesn't discuss failure modes or permission requirements.

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?

Four tight sentences, each earning its place, with the core action and the confirm-before-calling constraint front-loaded. No filler or restatement of the name.

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?

With no output schema, the description compensates by stating the return value (new id + browse URL). Combined with the 100%-covered input schema and safety annotations, an agent has enough to invoke correctly; minor gaps remain (no mention of permission scope or tag behavior beyond 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 description coverage is 100%, so the schema already documents all five parameters. The description's notes on the 'project' arg and on 'description' being plain text largely echo the schema, though the plain-text-to-HTML wrapping detail adds marginal value. Baseline 3 applies when the schema carries the load.

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?

States a specific verb+resource ('Create a new AzDO work item') and distinguishes itself from siblings azdo_get_work_item and azdo_search_work_items by being the creation path. An agent can tell what it does immediately.

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?

Gives an explicit, non-optional usage rule ('ALWAYS confirm with the user before calling — this is a mutating operation'), which is strong guidance. It does not name an alternative tool or describe when to prefer creating vs. updating/searching, but the confirmation precondition is clear and actionable.

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