podman_events

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the valuable behavioral detail that the event stream is bounded and will not hang, which is informative beyond the annotations. It does not disclose other traits such as filtering behavior or output format, so a 3 is appropriate.

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 exceptionally concise—two short sentences that convey the core purpose, the bounded non-blocking behavior, and a primary use case. Every word earns its place without unnecessary detail.

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?

With an output schema present and straightforward read-only operation, the description is adequate but leaves parameter semantics unexplained. It covers the tool's purpose and key behavior, but for a tool with 4 optional parameters, the lack of parameter guidance makes it only minimally complete.

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 adds no information about the parameters (limit, since, until, filters). The parameter names are somewhat self-explanatory, but the description does not compensate for the lack of schema descriptions, especially for time formats and filter syntax.

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 the tool reads the podman event stream and notes it is bounded and non-blocking. It gives a specific use case (troubleshooting timelines), but does not explicitly differentiate it from sibling tools like podman_container_logs, so it falls short of a 5.

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 provides a clear context for use ('good for troubleshooting timelines'), implying when to prefer this tool. However, it does not mention exclusions or explicitly name alternative tools, so it lacks the explicit when-not-to-use guidance that would merit a 5.

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