docker_logs

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the container must be running, how logs are truncated, or what the default output format is. The minimal description leaves critical details about side effects and requirements unspecified.

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 concise (one sentence), but this brevity sacrifices necessary detail. It is front-loaded with the main purpose, but lacks structure to convey key constraints or usage notes.

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?

Given the tool's function (log retrieval) and the lack of output schema, the description should explain what kind of logs are returned, any defaults, and prerequisites (e.g., container must exist). The current description is too sparse to allow an agent to use the tool correctly without additional knowledge.

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?

Only one parameter (tail) has a description in the schema. The description adds no additional meaning beyond the schema. Required parameters container and session_id are undocumented, and the description does not clarify their purpose or format. With 33% schema coverage, the description fails to compensate.

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 explicitly states the action (Get recent logs) and the resource (Docker container). It clearly distinguishes the tool from sibling tools like docker_ps (list containers) or docker_exec (execute commands). However, it could be more specific by mentioning that it retrieves the tail of 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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this is for viewing logs, while docker_exec is for interactive commands. The description lacks any context about typical use cases or preconditions.

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