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

With no annotations provided, the description carries the full behavioral disclosure burden. It adds meaningful non-obvious traits: only the SELECTed IDs are honored, the tool batch-fetches full fields, and it returns up to 50 items. It does not discuss authentication or errors, but the read-only search nature and return behavior are well covered.

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 compact and front-loaded with the core purpose. Every sentence adds value: the search intent, the projection alignment with azdo_get_work_item, the WIQL examples, and the behavioral caveat about SELECT clauses are all useful with no filler.

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?

The description is sufficient for correct invocation: it explains the query language, the required SELECT clause, the return projection, and the result cap. It does not detail error handling or authentication, but for a moderate-complexity read/search tool with no output schema, it covers the key operational facts well.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema by providing concrete WIQL examples and the guidance to 'Narrow WIQL for wider sweeps.' This adds practical parameter-construction value beyond the schema's own field descriptions.

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 states a specific verb and resource: 'Search AzDO work items with WIQL.' It also differentiates itself from related tools by referencing azdo_get_work_item's projection and by clarifying AzDO context versus Jira, so an agent can distinguish it from azdo_get_work_item, azdo_create_work_item, and jira_search.

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 clearly implies when to use the tool: when searching work items by query rather than fetching a single item. It gives WIQL examples and notes the same projection as azdo_get_work_item, which provides useful context, but it does not explicitly state an exclusion such as 'for a single item by ID, use azdo_get_work_item instead.'

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