ado_work_item_get

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

No annotations are present, so the description carries the behavioral burden. The verb 'Get' implies a read-only operation, and the description discloses that the response includes fields, relations, and revision. However, it does not mention permissions, error behavior, or how revisions are represented.

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 with no filler or redundant phrasing. It front-loads the core purpose and adds useful specifics about what is returned.

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 get-by-id tool this is close to minimal viable, but it lacks usage orientation among siblings and fails to explain the project parameter. Even with an output schema present, an agent has little guidance on when to choose this tool over ado_work_items_query or how the optional project context affects the call.

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 0%, and the description does not mention work_item_id or project at all. While work_item_id is somewhat self-evident from its name, the optional project parameter's role is completely unexplained, and the description adds no parameter-level meaning.

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 identifies the operation ('Get'), the resource ('a work item'), and the retrieval scope ('fields, relations, and revision'). This distinguishes it from sibling tools like ado_work_items_query and the create/update tools, though it does not explicitly say 'by ID' or name the distinguishing sibling.

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 provides no guidance on when to use this tool versus alternatives such as ado_work_items_query. It does not state any exclusions, prerequisites, or preferred selection context, leaving the agent to infer usage from the tool name alone.

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