check_kernel_ring_buffer

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

Discloses underlying commands (dmesg, journalctl -k) and default filtering behavior. However, does not explicitly state that it is read-only or any required privileges, but overall informative given no annotations.

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 with no fluff, front-loaded with purpose. Every sentence adds value.

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?

While the core behavior is clear, two parameters (lines, grep_pattern) are left unexplained, reducing completeness. Output schema exists but does not mitigate the missing parameter semantics.

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 the 'level' parameter is explained with examples; 'lines' and 'grep_pattern' are not described. With 0% schema description coverage, the description partially compensates but is incomplete.

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 retrieves kernel messages filtered by level, with explicit examples (e.g., 'err,warn'). It distinguishes itself from siblings like query_journalctl by focusing on hardware/driver issues.

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?

Suggests use for surfacing driver/hardware issues without reading full boot log, but does not explicitly mention when not to use or compare to alternatives like query_journalctl.

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