Get a work item

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

Discloses the full shape of the returned work item (description, assignees, labels, parent, cycle). No annotations exist, so it carries the burden well, though no mention of error handling or auth.

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?

Single sentence (17 words) with a parenthetical list. Front-loaded and efficient with 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?

Covers the primary purpose and return shape for a simple retrieval tool. Lacks error details but is sufficient given the tool's simplicity and sibling 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 already describes work_item_id as 'Work item id' with 100% coverage. Description adds minimal value beyond confirming id usage, so baseline 3 is appropriate.

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?

Clearly states the verb 'retrieve', resource 'work item', and scope 'by id'. The parenthetical list defines what 'full shape' includes, distinguishing it from list tools.

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?

Implies usage for single-item retrieval by id but lacks explicit guidance on when not to use or alternatives like list_work_items.

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