Get Docker Container Logs

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

Annotations indicate read-only, open-world, idempotent, non-destructive. The description adds: the reveal parameter is audited, and mismatched instance routing silently hits the wrong host. These are valuable beyond annotations. Could mention ratio limits or log format but still good.

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 sentences with zero filler. Every sentence adds value: first states purpose, second gives usage context and default. The schema descriptions are also concise. No wasted words.

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 log retrieval tool, the description covers key aspects: environment selection, a critical routing warning, and audit logging for sensitive data. No output schema, but the description does not need to explain return format. Minor gap: no mention of error cases or log line truncation.

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?

All parameters have schema descriptions (100% coverage). The description adds meaning by explaining the two instance environments, the audit behavior for reveal, and the routing warning for instance. This enhances understanding beyond the schema alone.

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 specifies the verb 'retrieve' and resource 'logs from a Docker container' with clarification about the target VPS environments (Hetzner prod by default, OrbStack dev). It distinguishes from sibling tools like vps_docker_ps and vps_docker_stats by focusing on 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 explicitly states the default target and how to switch to dev, and includes a critical warning about matching the Coolify instance to avoid silent routing errors. This provides clear when-to-use guidance, though it does not list explicit alternatives or when not to use.

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