list_work_item_enum_options

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining it resolves enum ids for validation and that unknown type falls back to a default. No contradictions.

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?

Two sentences, each essential. First sentence states purpose, second provides usage guidance and warning. No redundant text.

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?

Output schema exists, so return values are covered. Description covers purpose, usage, and a key pitfall (unknown type). Doesn't mention pagination but that is in schema with descriptions.

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 60% (some params like page_size, page_number have descriptions; field_id and work_item_type have examples). The description does not add per-parameter details but provides overall context. Baseline 3 with marginal compensation.

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?

Directly states it lists valid enum option ids for a work item field. Distinguishes from sibling tools by mentioning its use before create/update operations, and contrasts with list_document_enum_options for documents.

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?

Explicitly tells when to use: before create_work_items/update_work_items to resolve enum ids and avoid invalid enum errors. Also warns about unknown work_item_type silently falling back to ~, advising to verify the type id first.

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