Docker Logs

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'container logs' and reveals nothing about behavior such as whether it follows logs, applies limits, includes timestamps, requires container identification, or performs a read-only operation. This is effectively a restatement of the tool's name with no behavioral insight.

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 short, but this is under-specification rather than effective conciseness. It provides no front-loaded operational detail and no structure that helps an agent act on it.

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?

Despite the presence of an output schema, the description lacks any information about required inputs, supported options, or behavior. Given the large sibling set and the opaque 'params' schema, an agent cannot reliably select or invoke this tool correctly.

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 exposes a single free-form 'params' field with additionalProperties: true and zero documented subfields, and schema description coverage is 0%. The description does not explain what should go into 'params'—such as container ID, tail count, or filters—so the agent cannot construct a correct call.

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 'Логи контейнера' means 'container logs', which essentially restates the tool name and title without adding a specific verb or operation. It does not say whether this fetches, tails, searches, or streams logs, and it does not distinguish the tool from sibling logging tools like docker_events, docker_stats, or log_tail.

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?

There is no guidance on when to use this tool versus alternatives such as docker_events, service_logs, nginx_logs, or k8s_logs. No prerequisites, container selection method, or exclusions are mentioned, leaving the agent to guess when this tool is appropriate.

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