coolify_get_logs

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

No annotations are provided, so the description must fully disclose behavior. It only states 'retrieve logs' with filtering, but does not describe read-only nature, side effects, pagination, rate limits, or truncation behavior. The schema's 'tail' and 'limit' parameters hint at behavior, but the description adds no explicit 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?

The description is a single 18-word sentence that front-loads the action and resource, then lists filtering options concisely. It is efficient with no wasted words, though it could briefly mention the required 'uuid' parameter.

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?

With 7 parameters, no output schema, and no annotations, the description is inadequate. It does not indicate what the returned logs look like (e.g., array of objects, timestamps, structure), nor does it cover potential edge cases like empty results or error conditions. The filtering options are listed, but the overall behavior is underspecified.

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 coverage is 100%, so baseline is 3. The description summarizes 'filtering by level, time range, or text search', which provides a high-level grouping but no additional semantic meaning beyond the schema descriptions. It does not explain parameter interactions or constraints.

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 uses 'Retrieve logs for a Coolify application' which is a specific verb-resource combination. The tool name and context distinguish it from sibling log tools (get_database_logs, get_service_logs), but the description does not explicitly differentiate them.

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 sibling tools (e.g., database logs, service logs) or alternative tools like deployment logs. It does not mention prerequisites (e.g., UUID ownership) or when not to use it.

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