azuredevops_get_work_item

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

No annotations are supplied, so the description carries full disclosure burden. 'Get' implies a read-only operation and the project-discovery note addresses a prerequisite, but it says nothing about permissions/scopes, rate limits, or behavior of the expand/fields options. It adds modest value beyond a bare verb.

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?

Two tight sentences with the core action front-loaded and the prerequisite stated second. Nothing is wasted or buried.

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-item read tool with no output schema, the description tells the agent what is returned at a high level ('detailed information') and which keys identify the item. The enum semantics of expand are left to the schema, which is acceptable, but the description could say more about what 'detail' includes.

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 all four parameters are documented by the schema itself. The description only restates that ID is numeric and project is required/discoverable, adding no syntax or semantic detail beyond the schema — the baseline 3 for high coverage.

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 (Get), resource (Azure DevOps work item), and lookup key (numeric ID), which readily separates it from search_work_items, create_work_item, and update_work_item. It doesn't explicitly name a sibling alternative, keeping it just short of the top band.

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?

Usage is implied: fetch details for a work item whose ID is already known, in contrast to search_work_items. The line 'Project is required - discover it from project context' offers procedural guidance, but there is no explicit when-to-use/when-not framing or named alternative.

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