approvals_get_work_items_for_deployment

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description restates the endpoint and says nothing additional about pagination defaults, result limits, or whether 'all' conflicts with the paging parameters.

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?

A single short, front-loaded sentence with the endpoint appended; no wasted prose. The raw path is somewhat redundant with the annotation title but is brief.

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?

For a tool with 8 parameters, no output schema, and half the parameters undocumented, the description is too thin. It does not explain what a work item contains, how the type/state/expand filters behave, or how results are paginated.

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?

With 8 parameters at 50% schema description coverage, several properties (ids, type, state, expand) have no documentation anywhere. The description only echoes deploymentId from the path and adds no meaning about filtering, expansion, or how page/size interact with 'all'.

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 all work items for a deployment') and the path makes the scope concrete. It does not distinguish itself from the nearby siblings approvals_get_work_items or approvals_get_work_items_for_deployment_request, so an agent must infer the difference.

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 statement of when to use this versus the generic approvals_get_work_items or the deployment-request variant. The only clue is the path containing deploymentId, which is left implicit.

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