approvals_get_work_items

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds almost nothing on top: no pagination defaults, no ordering behavior, no indication of what a work item contains or whether unanswered items dominate results. The raw path string "GET /workitem/api/workitems" is the only extra content and carries no behavioral meaning.

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 short lines, purpose front-loaded, no filler prose. The trailing raw endpoint path duplicates the annotation title and could be dropped, but the overall size is tight.

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?

A seven-parameter paginated list endpoint with no output schema needs the description to say what comes back and how paging/filtering behaves; it does neither. Given the absence of an output schema and only partial parameter documentation, the definition leaves an agent under-equipped to call it correctly.

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 only 57% (type, state and assigneeState have no prose, only enums), and the description mentions no parameters at all. It does not explain that page/size control paging, that search covers deploymentName/work item name/workflow details, or how state and assigneeState interact — leaving the agent to read the schema cold.

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?

States a specific verb and resource ("Returns work items") plus the scope ("for the logged in user"), which is enough to separate it from approvals_get_work_item_by_id and approvals_get_work_items_for_deployment. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

There is no when-to-use guidance, no mention of the deployment-scoped and by-id siblings, and no explanation of when to apply the state/assigneeState filters versus when to call a different endpoint. The only hint is the implicit "logged in user" scope.

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