pve_get_node_syslog

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Read' implies a read-only operation, but there's no information about permissions required, rate limits, whether the log is real-time or historical, or what format the output takes. The description doesn't mention pagination behavior, error conditions, or any other behavioral characteristics beyond the basic read action.

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 at just three words. It's front-loaded with the core action and resource, with zero wasted words. While it may be too brief for optimal tool selection, it earns full marks for conciseness as every word contributes directly to the tool's purpose.

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?

For a read operation with 6 parameters and no output schema, the description is inadequate. It doesn't explain what the output looks like (log format, structure, typical content), doesn't mention any constraints or limitations, and provides no context about the system log's nature. With no annotations and no output schema, the description should do more to help an agent understand what to expect from this 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 100%, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema descriptions. It doesn't explain relationships between parameters (like how 'start' and 'limit' work together with 'since' and 'until'), nor does it provide examples or format details for date parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 system log' clearly states the action (read) and resource (node system log), but it's vague about scope and doesn't differentiate from similar sibling tools like pve_get_node_journal or pve_get_node_task_log. It provides basic purpose but lacks specificity about what kind of system log or what distinguishes it from other log-related tools.

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 multiple log-related tools in the sibling list (pve_get_node_journal, pve_get_node_task_log, pve_cluster_log), there's no indication of when this specific system log tool is appropriate versus other logging mechanisms. No prerequisites, exclusions, or alternative recommendations are mentioned.

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