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 discloses that it uses the calling user's stored credential, rejects inline credentials, returns an actionable error if AzDO is unconfigured, and returns HTML-stripped description text. Missing explicit read-only statement and not-found behavior, but generally transparent.

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 dense sentences, each with a distinct purpose: action, return fields, auth model, and error behavior. No filler or repetition; the most important identifying info is front-loaded.

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 usefully enumerates the returned fields and covers auth and error behavior. It does not mention what happens when the ID does not exist (e.g., null vs error), which is a minor gap for a simple get-by-ID 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 coverage is 100%, and the schema already fully documents the id parameter as a positive integer. The description merely repeats 'integer ID' without adding new semantic meaning, so baseline 3 is appropriate.

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 states a specific verb and resource ('Fetch a single Azure DevOps work item by integer ID') and clearly distinguishes from sibling search/create by emphasizing 'single' and 'by integer ID'. It does not explicitly name the sibling alternatives, so it falls short of the top score.

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 gives no explicit guidance about when to choose this tool over azdo_search_work_items or azdo_create_work_item. There is no mention of alternatives, prerequisites, or scenarios; usage context is only implied by the fetch-by-ID semantics.

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