coolify_get_application_logs

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. The description "Get application logs" does not reveal any behavioral information, such as whether it returns all logs, if there are limits, or if it is a read-only operation. The tool appears to be a simple retrieval, but the description lacks transparency.

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, consisting of a single sentence with no wasted words. However, it is so brief that it sacrifices informativeness for brevity. It is well-structured but lacks front-loading of critical details.

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 three parameters and no output schema, the description fails to explain what the tool returns (e.g., format of logs), how the parameters interact, or any default behavior. The tool is not fully described for an AI agent to use confidently without additional inference.

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 provides 100% coverage with descriptions for all three parameters (tail, uuid, since). The description adds no additional meaning beyond the schema, so it does not improve parameter semantics. Baseline score 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 "Get application logs" clearly states the action (get) and the resource (application logs), but it does not differentiate from sibling tools like coolify_get_application or coolify_get_server. The purpose is clear but could be more specific by mentioning the UUID parameter.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as when retrieving logs for a specific application versus using other log-related tools. There is no mention of prerequisites or context.

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