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

No annotations are provided, so the description carries the disclosure burden. It discloses credential handling (uses stored credential, no inline), notes HTML stripping behavior, and states it returns an actionable error if AzDO is not configured. These are genuinely useful behavioral details beyond what the schema conveys, though a read-only safety hint would have added more.

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 a compact three-sentence paragraph that front-loads the core purpose and return fields. It efficiently covers return format, credential semantics, and error behavior without wordiness. Loses one point for being a dense block rather than using clearer structural separators, though the density is justified by the field enumeration.

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 single-parameter read tool with 100% schema coverage and a detailed return-field list, the description is thorough. It discloses return fields, credential requirements, HTML-stripping behavior, and error handling. No output schema exists, so enumerating the return fields is appropriate and adequately compensates. The only minor gap is the absence of a declared read-only hint, which annotations would normally cover.

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 covers 100% of the single parameter with a clear description ('AzDO work item ID (e.g. 12345). Positive integer.'). The description reinforces the integer ID requirement and adds the return-field context that illuminates what the parameter drives, but doesn't need to elaborate further given the high schema coverage. Baseline 3 plus a small bonus for reinforcing the positive-integer constraint in prose.

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 opens with a specific verb+resource ('Fetch a single Azure DevOps work item by integer ID') and enumerates exactly which fields are returned. It clearly differentiates from siblings like azdo_search_work_items (search by query) and azdo_create_work_item (creation). The scope is precise and unambiguous.

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 states it uses the calling user's stored credential and does not accept inline credentials, providing useful contextual guidance. However, it does not explicitly say when this tool should be used versus alternatives like azdo_search_work_items, nor does it give exclusions. The credential disclosure is helpful but doesn't constitute full when-to-use guidance.

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