getWorkflowActionsForWorkItem

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

No annotations provided, so description must carry full behavioral disclosure. It only states 'Returns a list' without mentioning that it is read-only, whether pagination is applied (despite page_size/page_number parameters), or any auth requirements. This is insufficient for a tool with no annotation safety net.

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 one sentence, very concise, but too terse—it lacks necessary details like scope and usage context. While it is front-loaded, it does not earn its brevity by being complete.

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 5 parameters, no output schema, and no annotations, the description is incomplete. It omits return format, pagination behavior, and whether there are any side effects. The high parameter count and missing output schema demand more context.

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?

The input schema provides full descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description adds no additional semantics beyond what the schema already offers.

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 'Returns a list of Workflow Actions' clearly indicates the verb and resource. The tool name and required parameters (projectId, workItemId) specify the context, but the description itself does not explicitly state it is for a particular work item, which is a minor gap compared to siblings like getWorkflowActionsForTestRun.

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 tool versus alternatives. With many similar 'getWorkflowActionsForTestRun' and other get tools, the description lacks any contextual advice, making it hard for an agent to decide correctly.

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