list_work

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

No annotations provided, so description carries full burden. Discloses 'limited filtering support' but lacks details on pagination, rate limits, or potential side effects. Does not contradict annotations since none 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?

Relatively short (two sentences plus a bracket note). The note in brackets is slightly confusing but overall efficient. Could be more structured.

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?

No output schema, no annotations. Description covers filter and fields well but ignores attributes. Lacks specification of response format or pagination. Moderate completeness for a list tool with three parameters.

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%, baseline 3. Description adds value with an example for filter and explains that fields trims payload. Attributes parameter is not mentioned in description, so not fully leveraged.

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 'List work items using a filter string' with a specific verb and resource. Distinguishes from sibling by mentioning 'For portfolio-scoped project lists, use Beta MCP's listProjectsByPortfolioId instead.'

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 provides when to use ('LOCAL — query work items with filter') and when not to use ('limited filtering support, alternative for portfolio-scoped'). Gives examples and notes on field trimming.

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