arch_journalctl

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention output format, default number of lines, whether it is read-only, or how filters like errors_only behave. The only behavioral hint is 'via journalctl,' which indicates the underlying command but not the tool's own behavior.

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 a single, front-loaded sentence with no fluff. It states the essential purpose efficiently.

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?

Despite having an output schema, the tool has no annotations, zero parameter description, and lacks usage guidance. The description is too sparse for a tool with four parameters and a potentially complex return format. More detail on filtering, defaults, and output would be needed for an agent to use it correctly.

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 does not compensate by explaining any of the parameters (lines, unit_name, user_mode, errors_only). The parameter names are somewhat self-explanatory, but the description provides zero additional meaning beyond the schema.

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 a specific verb ('Fetch') and resource ('systemd service or kernel logs') via journalctl. It distinguishes this tool from siblings like arch_systemctl (service management) and arch_get_system_info, which do not fetch 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?

The description implies usage when systemd service or kernel logs are needed, but does not explicitly state when to use this tool over alternatives or mention any exclusions. It provides no context on when journalctl would be preferred over arch_systemctl or other diagnostic tools.

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