pve_node_dns

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

The description declares the tool as read-only, which is a key behavioral trait. However, with no annotations, it does not disclose potential error conditions, permission requirements, or other side effects, leaving some gaps for a fully transparent understanding.

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 concise, consisting of two essential sentences. It front-loads the purpose and return type, and efficiently points to the sibling for mutation. Slight room for improvement by integrating parameter hints, but overall efficient.

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?

The description covers the core purpose and return format, and with an output schema present, it is fairly complete for a simple read operation. However, it omits details about the 'node' parameter and any potential errors, which could affect usability in complex scenarios.

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 does not elaborate on the parameters beyond what the schema provides. With 50% schema description coverage (only 'proximo_target' described), the 'node' parameter lacks explanation, and the description adds no additional meaning to the parameters, making it harder for the agent to know what to pass.

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?

Clearly states 'Read a Proxmox node's DNS configuration (read-only)' and specifies the return format. Distinguishes from sibling 'pve_node_dns_set' for changing config, establishing a clear purpose.

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?

Explicitly directs to use 'pve_node_dns_set' to change the configuration, providing a clear alternative. Lacks explicit 'when not to use' statements, but the context sufficiently guides usage.

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