Get work item

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and side-effect profile is fully covered without the description. The description adds only modest value by hinting at returned content ('description and tags'), but says nothing about error behavior for missing IDs or pagination, which is acceptable at this bar.

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?

A single compact sentence that front-loads the action and resource, with the scope qualifier and returned fields trailing efficiently. No wasted words.

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 simple two-parameter read tool whose annotations already cover the safety profile, the description is minimally adequate, but with no output schema and an undocumented 'id' parameter it should do more to clarify the identifier semantics and confirm what a 'full details' payload contains.

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 only 50%: 'project' is documented as an Azure DevOps project name, but 'id' has no description anywhere. The description says nothing to clarify that 'id' is a work item identifier or its expected form, so it fails to compensate for the coverage gap.

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?

The description states a specific verb and resource ('Get full details of one work item') and scopes it to a single item, which implicitly contrasts with the list-oriented sibling search_work_items. However, it never names or explicitly contrasts that alternative, so the differentiation is left to inference.

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 singular 'one work item' implies this is the single-item retrieval path as opposed to search_work_items or list_projects, but there is no explicit when-to-use statement, no prerequisite note (e.g., needing a known ID), and no exclusion guidance. Usage is implied rather than stated.

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