Get work item delivery trace

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does convey a read-only relationship-traversal behavior and lists the artifact types returned, but it does not mention output shape, pagination, authentication requirements, or behavior when no linked artifacts exist.

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 front-loaded sentence with no filler. Every word adds specificity about what the tool traces and what the result contains.

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?

There is no output schema or annotation coverage, so the description must explain both inputs and expected results. It does name the return categories, which is helpful, but it omits project parameter semantics, response structure, and edge cases. For a simple read-only trace tool this is nearly adequate but still has clear gaps.

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%, so the description must compensate for parameter meaning. It only indirectly implies workItemId via 'a work item' and never explains the optional project parameter or why it might be needed. The schema's raw types do not tell the agent the semantic role of either parameter.

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 uses a specific verb, 'Trace,' and identifies the exact resource and result categories: linked pull requests, commits, builds, branches, and related work items. This clearly distinguishes it from sibling tools like get_work_item or query_work_items, which retrieve a work item's own data rather than its delivery trace.

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 implies the right use case: when an agent needs the delivery/link graph around a work item rather than the work item's fields or comments. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for selection among the sibling tools.

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