pve_node_time_get

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

No annotations are provided, so the description carries the full burden. It declares the tool as READ-ONLY and discloses the return format (a dict with specific keys). It also adds a verification note. However, it does not discuss authentication or error cases, but the simplicity of the operation mitigates the gap.

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 three sentences, each serving a distinct purpose: identifying the tool as read-only, providing API details and verification, and offering sibling guidance. No unnecessary words; front-loaded with 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?

Given full schema coverage and the presence of an output schema, the description covers the essential behavioral aspects (read-only, return keys). It also mentions live verification, adding confidence. For a simple read tool, this is complete.

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?

Input schema coverage is 100%, so the schema already documents all parameters. The description adds minimal extra value beyond mentioning the node parameter implicitly. The sibling reference is helpful but does not enhance parameter understanding.

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 is READ-ONLY and 'get the current time and timezone of a PVE node.' It specifies the verb (get) and resource (time and timezone), and references a sibling tool for changing timezone, distinguishing it from alternatives.

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 explicitly directs to pve_node_time_set for changing timezone, providing an alternative. It does not elaborate on when to avoid using it, but the read-only nature and default node parameter imply low barriers. A slight improvement would be to note querying an unavailable node.

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