search_work_items

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

No annotations provided, so description carries full burden. It only states purpose and does not disclose any behavioral traits (e.g., pagination, limits, permission requirements, response structure). Schema hints at output schema but description adds no depth.

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 is concise but lacks substance. While not verbose, it sacrifices informativeness. Every word is used, but it does not fully leverage the space to add value.

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 documented. However, given the tool's complexity (6 parameters, similar siblings), the description is too brief to provide complete context. It fails to explain when to choose this over 'list_work_items' or other search-like tools.

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?

Input schema has 100% description coverage for all 6 parameters, so the schema already documents them. The description adds no extra meaning beyond what the schema provides, meeting the baseline expectation.

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?

Description clearly states it searches work items across a workspace, using verb 'Search' and resource 'work items'. It distinguishes from 'list_work_items' (enumerate) and 'retrieve_work_item' (single item) by implying query-based retrieval. However, could be more specific about the search scope (e.g., free-form text) which is only in schema.

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?

No guidance on when to use this versus siblings like 'list_work_items' or 'retrieve_work_item'. The description does not specify context or alternatives, leaving the agent to infer from the name and schema alone.

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