coolify_list_service_scheduled_tasks

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states the basic action. It omits whether the operation is read-only, requires specific permissions, returns all tasks or paginates, or any error conditions. This leaves the agent with insufficient behavioral context.

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, clear sentence that efficiently conveys the core purpose. No superfluous words. For such a simple tool, this is appropriately concise, though slightly more context could be beneficial without harming conciseness.

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?

The tool is simple (one parameter, no nested objects, no output schema). However, the description does not explain what the response contains (e.g., list of scheduled tasks with their IDs, commands, cron expressions). An agent lacks clarity on the return format, which is important for invocation. Given low complexity, 3 is adequate but not complete.

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 has 100% description coverage for the only parameter (`uuid`), whose schema description already explains it is 'UUID of the service'. The tool description adds no further meaning or usage details beyond that, so baseline 3 is appropriate.

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 'List all scheduled tasks for a Coolify service' uses a specific verb ('List') and identifies the resource ('scheduled tasks') scoped to a service. It clearly distinguishes from sibling tools like `coolify_list_application_scheduled_tasks` (for applications) and `coolify_list_service_scheduled_task_executions` (for 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 (e.g., create, update, delete, or execution listings). It lacks explicit context for usage, prerequisites, or conditions that would help an agent choose correctly among many sibling tools.

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