get_docker_container_logs

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

With no annotations supplied, the description carries the safety burden; 'Safley read' and the limitation to 'recent log lines' with a maximum of 1000 convey a read-only, bounded operation. It also discloses the return type as a JSON string. It does not mention error cases or prerequisites, but the core behavioral profile is clear.

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 compact, front-loaded with the one-sentence purpose, and organized into Args/Returns sections with no filler. Every sentence contributes useful information.

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 two-parameter read tool with an output schema and no annotations, the description covers purpose, parameter semantics, output format, and operational bounds. Nothing an agent needs to invoke it correctly is missing.

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 0%, and the description fully compensates: it explains that container_name accepts a name or short/full ID, and that lines_count controls recent-line volume with default and max. This adds meaning well beyond the bare schema properties.

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 states a specific verb ('read'), a specific resource ('stdout/stderr logs from a specific Docker container'), and clearly distinguishes itself from siblings like read_service_logs and list_docker_containers. The scope is explicit and immediately actionable.

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 makes clear the tool applies to Docker containers, but it never explicitly says when to choose it over read_service_logs or list_docker_containers, nor does it mention exclusions. Usage guidance is only implied by the tool name and 'Docker container' wording.

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