List Coolify Applications

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. Description adds context about default compact output, the trade-off of passing summary:false for full objects (large), and the reveal parameter disclosing secrets. No contradictions.

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?

Two sentences, both essential. First sentence covers purpose and default behavior; second explains the key parameter trade-off. No fluff, perfectly front-loaded.

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's simplicity (listing applications with two boolean parameters and one enum), the description covers the main points: what it returns by default, how to get full objects, and the reveal option. Could mention pagination or limits, but not critical for typical use. Output schema not provided but description compensates.

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 covers all parameters with descriptions (100% coverage), so baseline is 3. Description adds extra meaning by explaining the summary parameter's effect (compact vs full objects) and the reveal parameter's security implication, providing value beyond the schema.

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?

Description clearly states 'List all applications across the Coolify instance' with specific verb and resource. It distinguishes from sibling tools like coolify_get_application by indicating it returns all applications, and from other list tools by specifying the 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?

Description states what the tool does but does not explicitly compare to alternatives or provide when-to-use/when-not-to-use guidance. The sibling list includes many similar list functions, but no differentiation or usage context is given.

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