pve_node_journal

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

With no annotations, the description carries the burden and discloses key behaviors: it is a read operation, returns 'log-line strings', and has a cap of 5000 entries. This is sufficient for a non-destructive tool, though it could mention authorization requirements.

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 extremely concise with two sentences that convey purpose, type, and a key constraint. Every word adds value, and critical information is front-loaded.

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?

Given the presence of an output schema, the description omits return value details but specifies the return type (log-line strings). It could mention pagination or empty results, but overall it provides enough context for a simple fetch tool.

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 low (20%), and the description only adds context for the 'lastentries' parameter (cap of 5000). Parameters like 'node', 'since', and 'until' are left without explanation, relying on the schema which has minimal descriptions.

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 action ('Fetch'), resource ('journal entries from a PVE node'), and type ('read; returns log-line strings'). It distinguishes from sibling tools like pve_node_syslog by specifying 'journal entries'.

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 for fetching journal entries but provides no explicit guidance on when to use this tool versus alternatives such as pve_node_syslog or pve_node_status. No exclusions or context are given.

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