Get work item

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

With no annotations provided, the description carries the behavioral disclosure burden. The phrase 'including all fields and relations by default' usefully discloses the default expansion behavior, which is meaningful beyond the schema. However, it does not mention read-only status or response characteristics, but 'Get' makes the read-only intent reasonably clear.

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 single concise sentence that states the tool's core purpose and its default output behavior with no filler. It is appropriately front-loaded and easy to parse.

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 get-by-ID operation, the description is adequate, but with no output schema and no annotations it leaves some contextual omissions, such as return shape and default project behavior. The schema covers parameter details, but the overall description could add more value around invocation context.

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% and already explains each parameter, so the description adds little extra parameter meaning. The default-expansion note lightly reinforces the expand field's behavior, but no additional semantics beyond the schema are provided.

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 clearly states a specific action ('Get') and resource ('one Azure Boards work item by ID'), and clarifies scope as a single item fetched by ID. This distinguishes it from list/query tools like query_work_items and get_work_item_delivery_trace without needing to inspect schemas.

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?

There is no explicit guidance for when to use this tool versus alternatives. It does not mention that query_work_items is for filtering/searching or that get_work_item_delivery_trace exists, so an agent gets no explicit routing guidance beyond the inherent meaning of 'by ID.'

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