list_running_executions

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

Beyond the readOnlyHint annotation, the description reveals a fallback mechanism: it tries the API status filter first and then scans recent executions for missing stop times. This adds valuable behavioral insight that annotations alone do not provide.

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 extremely concise with only two sentences. The core purpose is front-loaded in the first sentence, and the second sentence adds essential behavioral detail without any redundancy.

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?

Given the simplicity of the tool (one parameter, no nested objects, no output schema), the description covers the core functionality and fallback behavior. It does not specify return fields, but this is tolerable for a list tool likely returning standard execution objects.

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 fully describes the single parameter maxItems with a description, so schema coverage is 100%. The description offers no additional explanation of the parameter's meaning or usage, meeting the baseline without exceeding.

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 clearly states the tool lists executions currently running or waiting in the queue, using a specific verb-resource combination ('list executions') and distinguishing it from generic list tools like list_executions.

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 does not provide guidance on when to use this tool versus alternatives such as list_executions or other sibling tools. The phrase 'Queue-mode view' hints at context but lacks explicit comparison or exclusion conditions.

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