coolify_list_service_scheduled_task_executions

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

No annotations are provided, so the description must disclose behavioral traits. It does not state whether this is a read-only operation (implied by 'List'), any rate limits, pagination behavior, or ordering of results. The description only restates the purpose without adding behavioral nuance.

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 a single clear sentence with no wasted words. It is appropriately sized for a simple list tool and front-loads the action ('List') and target ('executions of a scheduled task').

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 tool has 2 required parameters, no output schema, and no annotations, the description is too minimal. It does not explain the result format, whether filtering or sorting is supported, or how to interpret the execution data. The sibling tools include many similar list operations, and the description fails to help an agent understand unique constraints or usage 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for the two parameters (uuid and task_uuid). It does not explain how to obtain these UUIDs or specify their source (e.g., from the service or task list tools).

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 of a scheduled task for a service, using a specific verb ('List') and resource ('executions of a scheduled task for a Coolify service'). It effectively distinguishes from sibling tools like 'coolify_list_service_scheduled_tasks' which lists tasks, not 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 provides no guidance on when to use this tool versus alternatives. While it is clear what it does, there is no mention of prerequisites (e.g., needing a service UUID and task UUID), no context about the relationship to other list tools, and no exclusion criteria.

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