coolify_get_database_logs

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

The annotation declares readOnlyHint=true and idempotentHint=true, so the read-only nature is already covered. The description adds a valuable behavioral detail: 'Secrets are redacted,' which is beyond what annotations provide. This is useful context for the agent.

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 two short sentences: 'Get database container logs. Secrets are redacted.' Every word adds value, with no redundancy or fluff.

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 read-only log-fetching tool with high schema coverage and annotations, the description is adequately complete. It covers the core function and a key behavior (redaction). It does not describe output format or default line counts, but these are either specified in the schema (lines default) or not critical for execution.

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 description coverage is 100%, with both 'database_uuid' and 'lines' having descriptions in the schema. The tool description does not add additional parameter meaning, but the schema already documents them well, 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 clearly states 'Get database container logs' with a specific verb and resource. It distinguishes from sibling tools like get_application_logs and get_service_logs by explicitly targeting database logs.

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 indicates the tool is for database container logs, which implies when to use it, but it does not explicitly mention alternatives or exclusions. The sibling tool names suggest differentiation, but the description itself lacks direct guidance on choosing this over get_service_logs or get_application_logs.

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