coolify_list_resources

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

The description adds the filter list, which is behaviorally relevant, but the read-only and idempotent nature is already disclosed by annotations. No additional behaviors like pagination or ordering are described.

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, efficient sentence that front-loads the action and lists filters. Every word earns its place, with no 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?

For a simple filter list with strong annotations and full schema coverage, the description is nearly complete. It clearly states the function and filters, though it omits details about return value or pagination, which are not critical given the 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 schema already includes comprehensive descriptions for all five parameters (100% coverage). The tool description merely lists the parameter names without adding new semantic details, so the baseline of 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 clearly states the tool's action (list) and resource (resources), and enumerates the filter parameters. This differentiates it from sibling tools like coolify_list_servers (lists servers) and coolify_get_resource (gets a single resource).

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 implies this is the general resource listing tool with filters, but does not explicitly state when to use it vs alternatives. No mention of when to prefer coolify_list_server_resources or coolify_project_overview.

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