pve_set_node_time

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. 'Set node timezone' implies a mutation operation, but it doesn't disclose whether this requires specific permissions, whether it's destructive (e.g., affects running services), what happens on failure, or if there are rate limits. For a system configuration tool with zero annotation coverage, this is inadequate.

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 maximally concise with just three words that directly convey the core functionality. There's zero wasted language, and it's perfectly front-loaded with the essential information. This is an excellent example of efficient communication.

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 mutation tool that changes system configuration with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'setting the timezone' entails (e.g., does it require a reboot?), what permissions are needed, potential side effects, or what constitutes success/failure. The agent would have significant gaps in understanding how to use this tool appropriately.

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?

The description adds no parameter information beyond what's already in the schema (which has 100% coverage with clear descriptions for both parameters). The schema already documents 'node' as 'Node name' and 'timezone' as 'Timezone (e.g., Europe/London)', so the description provides no additional semantic value. Baseline 3 is appropriate when the schema does all the work.

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 verb ('Set') and resource ('node timezone'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'pve_set_node_dns' or 'pve_set_cluster_firewall_options' which also modify node/cluster settings, so it doesn't fully distinguish itself within the family of 'set' operations.

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. It doesn't mention prerequisites (e.g., needing administrative access), when this operation is appropriate (e.g., during maintenance windows), or what happens if the timezone is invalid. With many sibling tools available, this lack of contextual guidance is a significant gap.

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