pve_get_node_journal

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Read node journal' implies a read-only operation but doesn't specify authentication requirements, rate limits, output format, pagination behavior, or whether this returns real-time streaming data versus historical logs. For a tool with 5 parameters and no annotation coverage, this is insufficient behavioral context.

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 just three words, front-loading the essential information. There's zero wasted language or unnecessary elaboration, making it easy to parse quickly.

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 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'node journal' contains versus other logs, doesn't clarify the relationship between parameters (e.g., how 'since/until' interact with 'lastentries'), and provides no information about return format. For a data retrieval tool with filtering parameters, more context is needed.

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 100%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond the schema's documentation of node, since, until, lastentries, and service. This meets the baseline expectation when schema coverage is complete.

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 'Read node journal' clearly states the action (read) and resource (node journal), which is specific enough to understand the basic purpose. However, it doesn't differentiate from sibling tools like 'pve_get_node_syslog' or 'pve_get_node_task_log' that also retrieve log-like data from nodes, leaving ambiguity about when to choose this particular journal-reading tool.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools that retrieve node-related data (e.g., pve_get_node_syslog, pve_get_node_task_log, pve_cluster_log), there's no indication of what makes the node journal distinct or when it should be preferred over other logging tools.

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