event_list

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

Discloses return structure (JSON with events, returned, limit, truncated) and warns about truncated results with actionable advice to increase limit. No annotations exist, so description carries full burden and delivers well.

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?

Well-structured with a clear first line, followed by use case and a formatted Args block. Not overly verbose, though the Args section could be more integrated.

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?

Covers return format, pagination behavior, and all parameters. No output schema, yet description fully compensates. For a list tool with three optional params, this is comprehensive.

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 0% but the 'Args' section explains all three parameters (namespace, limit, target) with practical details (e.g., 'omit for all namespaces'). Adds meaning beyond schema names and types.

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 'List recent events' and specifies returned fields (type, reason, object, message, age). The [READ] prefix and diagnostic use case distinguish it from sibling tools like pod_list or node_list.

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?

Explicitly mentions diagnosing pod starting issues (FailedScheduling), providing direct context. Does not state when not to use or alternatives, but the context is clear enough for appropriate selection.

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