docker_events_summary

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

Declares 'Read-only' and provides return format, but no further behavioral details (e.g., rate limits, authentication). With no annotations, the description carries the burden, and it meets a basic level.

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?

Two concise sentences, front-loaded with action and specifics. 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?

Provides enough context for a simple tool: explains events, return format, and parameter role. No output schema, but return structure is described. Could mention if there's pagination or limits.

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 coverage is 100%, so baseline is 3. Description adds little beyond schema (e.g., 'lookback window' echoes since_minutes description). No extra meaning for instance_id.

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?

Clearly states it aggregates specific container lifecycle events (die/oom/restart/kill/start) on one instance over a lookback window, distinguishing it from sibling tools like docker_ps or docker_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?

Implies usage context (aggregating events on one instance) but does not explicitly state when not to use or mention alternatives. However, the sibling list and clear purpose make it relatively clear.

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